Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ease-dev] Oomph Setup failed

2017-01-09 21:16 GMT+01:00 Christian Pontesegger <christian.pontesegger@xxxxxx>:
>
>
> On 09.01.2017 20:49, Raphael Geissler wrote:
>>
>> I am new in the the Eclipse community, but I have certainly a few
>> ideas for scripts, that I can provide and blog about.
>
> That would be great. Blogging is also a valuable contribution as it helps to
> spread the word and lure other people to the project.
>
>>
>>> And of course documentation is always needed (I know, its boring :))
>>
>> Yes, that seems to be an issue, I would say. :) I started with that:
>> https://rage5474.github.io/2017/01/08/Eclipse-Scripting-Basics-EASE.html
>> Maybe you or anyone can review it. A link to it would also be good. My
>> blog is not that popular.
>
> You could write a 'getting started' section. Instead of pushing it to github
> I would appreciate to have it in the eclipse wiki. If you are interested you
> could also provide some help pages to o.e.ease.help. The eclipse help uses
> plain html pages. To register them you need some xml, but I can hep out here
> in case you do this for the first time.

You're right general things should be in the Eclipse wiki, but it is
not that fancy. :)
So if you tell me how this works, I can merge the content of my blog
to the wiki and extend it there.

> For your blog: as I can see it will deal mostly with eclipse topics, so you
> could promote it on http://www.planeteclipse.org/planet/
> You should find a link there to add your own blog.

Found it. Thanks.

>> Let me start with Cron stuff...Do you have there more 'requirements'?
>> As I said I am new in the Eclipse Community, maybe you have to help me
>> with some practical things as soon as I have code to integrate.
>
> I would expect it to accept the same syntax as cron does:
> https://en.wikipedia.org/wiki/Cron
>
> possibly everything after the time schedule could be passed to the executed
> script as an argument.
>
> eg:
> /*
> * cron: 33 15 * * * param1 param2
> */
>
> print("To be executed daily at 15:33")

Ok. But what should happen with the parameters? Should it come back to
the script as parameter?
Do you have an example for me?

As soon as my setup is working, I will give it a try.

Quartz seems to have a cron trigger. It is license under Apache 2.0.
Can we use that?
See: http://www.quartz-scheduler.org/documentation/quartz-2.1.x/examples/Example3.html


> Christian
>
> _______________________________________________
> ease-dev mailing list
> ease-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/ease-dev


Back to the top