[lwip-users] Disconnect client from LWIP server on various occassions

[Matthias Paul]

Hello LWIP users,

currently using raw API for LWIP server implementation.

1. When the network cable is disconnected, I'd like to disconnect all 
clients connected to my LWIP server, otherwise those connections are 
kept connected from the server side.
Installed the callback for netif changes (see 
netif_set_status_callback()). The callback _is_ called. Now it's not 
clear to me how to close all connections assigned to that network 
interface. Should I iterate over linked list tcp_active_pcbs (declared 
in tcp_priv.h) and close them all? Or is there a better way?


2. Based on tcpecho_raw example in contribution package 2.1.0 
(contrib2.1.0/apps/tcpecho_raw/):
If the received pbuf pointer in tcpecho_raw_recv() is NULL, the 
connection has been closed by the remote. Now the code waits to send out 
all unsent data before actually closing the connection:


 (p == NULL) {
    /* remote host closed connection */
    es->state = ES_CLOSING;
    if(es->p == NULL) {
  /* we're done sending, close it */
  tcpecho_raw_close(tpcb, es);
    } else {
  /* we're not done yet */
  tcpecho_raw_send(tpcb, es);
    }
    ret_err = ERR_OK;
  }

If the LWIP server sends a long data stream (some megabytes of data) 
while receiving the remote disconnect, I'll run into problems because 
the server stalls: tcp_sent() is never called afterwards, so the server 
cannot push further data to the client . Can anyone explain why the 
connection isn't closed instantly by call to tcpecho_raw_close()?



Thank you for reading,

Paul


___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users

[lwip-users] tcp_sent() callback: Called once per sent packet or for multiple packets at once?

[Matthias Paul]

Hello all,

I'm using lwip 2.1.2 in non-OS / non-threaded mode (main loop mode) with 
raw API to send/receive TCP packets.


When sending packets with tcp_write() I'd like to use zero copy 
mechanism. Therefore I need to keep the pbuf objects until the buffer 
has been sent and acknowledged by the recipient. When acknowledged, my 
callback registered by tcp_sent() is called:


static err_t

TCPSERVER_sentCallback(

    void                        * arg,

    struct tcp_pcb                * tcpPcb,

    uint16_t                    length) {

   // remove pbuf which are reported as "sent"
   ...
}

Is "length" always matching a single pbuf length or could it happen that 
TCPSERVER_sentCallback() reports multiple pbuf objects at once?


Also, can I assume, that TCPSERVER_sentCallback() is called in the order 
the packets have been sent?



Thank you for reading,

Paul
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users

Re: [nebula-dev] CDateTime: how to CSS style the toolbar of the date picker?

[Matthias Paul Scholz]

Hi Laurent,

Great!
As a matter of fact, I do not need it immediately, but somewhere in the
next three months would be great.

Thanks,
  MP

Am So., 4. Juli 2021 um 22:25 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Matthias,
>
> I've created a new bug for this new feature (
> https://github.com/eclipse/nebula/issues/355), and it is closed (for real
> ;) )
> The documentation (https://wiki.eclipse.org/Nebula_CSS_CDateTime) has
> been updated too.
>
> If you need a new release of Nebula (2.5.1), feel free to ask.
>
> Cheers,
>
> Laurent
>
> Le jeu. 1 juil. 2021 à 18:51, Laurent Caron  a
> écrit :
>
>> Hi Matthias,
>>
>> Agghh I think I've made a mistake, because the branch has not been
>> merged :'(
>>
>> I propose you to work on this topic tomorrow, and if you need a new
>> release I will create one (and the documentation will be updated).
>>
>> Sorry,
>>
>> Laurent
>>
>>
>>
>> Le mer. 30 juin 2021 à 14:22, Matthias Paul Scholz <
>> matthias.paul.sch...@gmail.com> a écrit :
>>
>>> Hi Laurent,
>>>
>>> I have seen that #572033 is fixed in the new Nebula 2.5.0 release.
>>> Thank you very much for this! :)
>>>
>>> Yet, I could not find any documentation on the actual css properties
>>> that can be used to style the color of the ok, cancel and clear button in
>>> the toolbar of the CDateTime widget now.
>>> Maybe you could provide me with a hint?
>>>
>>> Best,
>>>   MP
>>>
>>>
>>>
>>> Am Mi., 17. März 2021 um 14:38 Uhr schrieb Matthias Paul Scholz <
>>> matthias.paul.sch...@gmail.com>:
>>>
>>>> Thanks Laurent!
>>>>
>>>> Here we go: https://bugs.eclipse.org/bugs/show_bug.cgi?id=572033
>>>>
>>>> Best,
>>>>   MP
>>>>
>>>> Am Mi., 17. März 2021 um 13:51 Uhr schrieb Laurent Caron <
>>>> laurent.ca...@gmail.com>:
>>>>
>>>>> Hi Matthias,
>>>>>
>>>>> Yes, everything is possible for the Nebula Commiters ;)
>>>>>
>>>>> Please fill a bug :
>>>>> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Nebula
>>>>>
>>>>> I'll work on this topic this week
>>>>>
>>>>> Thank you for your feedback,
>>>>>
>>>>> Laurent
>>>>>
>>>>> Le mer. 17 mars 2021 à 08:40, Matthias Paul Scholz <
>>>>> matthias.paul.sch...@gmail.com> a écrit :
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Thanks to the efforts of Laurent, the CDateTime can be styled using
>>>>>> the Eclipse CSS styling feature. :)
>>>>>>
>>>>>> However, there seems to be some gap still: I could not find a
>>>>>> possibility to style the colors of the buttons and of the text in the
>>>>>> toolbar of the date picker in graphical mode, .i.e. the ok, cancel and
>>>>>> "clear" buttons.
>>>>>>
>>>>>> In particular the  (by default dark gray) "clear" button is almost
>>>>>> invisible on a dark background.
>>>>>>
>>>>>> is is possible to style these buttons somehow?
>>>>>>
>>>>>> Best and thanks,
>>>>>>   MP
>>>>>> ___
>>>>>> nebula-dev mailing list
>>>>>> nebula-dev@eclipse.org
>>>>>> To unsubscribe from this list, visit
>>>>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>>>>
>>>>> ___
>>>>> nebula-dev mailing list
>>>>> nebula-dev@eclipse.org
>>>>> To unsubscribe from this list, visit
>>>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>>>
>>>> ___
>>> nebula-dev mailing list
>>> nebula-dev@eclipse.org
>>> To unsubscribe from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>
>> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] CDateTime: how to CSS style the toolbar of the date picker?

[Matthias Paul Scholz]

Hi Laurent,

I have seen that #572033 is fixed in the new Nebula 2.5.0 release.
Thank you very much for this! :)

Yet, I could not find any documentation on the actual css properties that
can be used to style the color of the ok, cancel and clear button in the
toolbar of the CDateTime widget now.
Maybe you could provide me with a hint?

Best,
  MP



Am Mi., 17. März 2021 um 14:38 Uhr schrieb Matthias Paul Scholz <
matthias.paul.sch...@gmail.com>:

> Thanks Laurent!
>
> Here we go: https://bugs.eclipse.org/bugs/show_bug.cgi?id=572033
>
> Best,
>   MP
>
> Am Mi., 17. März 2021 um 13:51 Uhr schrieb Laurent Caron <
> laurent.ca...@gmail.com>:
>
>> Hi Matthias,
>>
>> Yes, everything is possible for the Nebula Commiters ;)
>>
>> Please fill a bug :
>> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Nebula
>>
>> I'll work on this topic this week
>>
>> Thank you for your feedback,
>>
>> Laurent
>>
>> Le mer. 17 mars 2021 à 08:40, Matthias Paul Scholz <
>> matthias.paul.sch...@gmail.com> a écrit :
>>
>>> Hi all,
>>>
>>> Thanks to the efforts of Laurent, the CDateTime can be styled using the
>>> Eclipse CSS styling feature. :)
>>>
>>> However, there seems to be some gap still: I could not find a
>>> possibility to style the colors of the buttons and of the text in the
>>> toolbar of the date picker in graphical mode, .i.e. the ok, cancel and
>>> "clear" buttons.
>>>
>>> In particular the  (by default dark gray) "clear" button is almost
>>> invisible on a dark background.
>>>
>>> is is possible to style these buttons somehow?
>>>
>>> Best and thanks,
>>>   MP
>>> ___
>>> nebula-dev mailing list
>>> nebula-dev@eclipse.org
>>> To unsubscribe from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Close bugzilla?

[Matthias Paul Scholz]

+1 from me

Am Mo., 21. Juni 2021 um 12:22 Uhr schrieb Christoph Läubrich <
lae...@laeubi-soft.de>:

> I must confess I haven't noticed that there is bugzilla (also) beside
> github anyways :-D
>
> Am 21.06.21 um 10:42 schrieb Wim Jongman:
> > Hi,
> >
> > Many projects are closing Bugzilla. I propose to close our Bugzilla and
> > move to Github issues.
> >
> > Cheers,
> >
> > Wim
> >
> > ___
> > nebula-dev mailing list
> > nebula-dev@eclipse.org
> > To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
> >
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [lwip-users] Out of memory in PCP_PCB pool after 2^32 milliseconds

[Matthias Paul]

Hello Adam,

LWIP uses the TIME_LESS_THAN macro to handle integer overflows. Please 
have a look at the usage in /core/timeouts.c/ in /sys_check_timeouts()/:


/* Check if timer's expiry time is greater than time and care about u32_t 
wraparounds */

#define TIME_LESS_THAN(t, compare_to) ( (((u32_t)((t)-(compare_to))) > 
LWIP_MAX_TIMEOUT) ? 1 : 0 )

Paul


Am 28.05.2021 um 21:25 schrieb vysocan [via lwIP]:

Hello Trampas,

thanks for the hints. I initialized the sys ticks with 2^32 - 120 
seconds, and I got mqtt pbuf=NULL in around 120 seconds + 120 keep 
alive seconds.


The ChibiOs sys_arch.c port includes sys_now() (current time in 
milliseconds) following simplified implementation:

  return ((u32_t)chVTGetSystemTimeX() - 1) / 10 + 1;
Since it ticks at 100 uS.

I guess it might cause the problems as it overflows back to 0 leaving 
the lwip timers waiting for value higher than (2^32)/10.


To support my guess, I turned on another debug option and last lwip 
timer message I see is:

sys_timeout: 2000C5DC abs_time=429497730 handler=ip_reass_tmr arg=805B28C


Adam

pá 28. 5. 2021 v 13:45 odesílatel Trampas Stern <[hidden email] 
> napsal:


Increase the counter to a uint64_t.

You can also start the counter at something other than zero to
prove root cause faster.

Trampas

On Fri, May 28, 2021 at 7:08 AM Adam Baron <[hidden email]
> wrote:

Czesc Tomek :),

I'll try to add it. Thanks.

However, I feel like it is rather related to the problem of
overflowing a uint32 counter of some kind. Since the TCP_PCBs
are not freed after 2^32 ticks.

Adam

pá 28. 5. 2021 v 9:44 odesílatel Tomasz W <[hidden email]
> napsal:

Hi (Cześć)
Lok for this

https://lists.nongnu.org/archive/html/lwip-devel/2020-12/msg00014.html


In my case it solved the problem of the web server dying
after a few days


pt., 28 maj 2021 o 08:58 Adam Baron <[hidden email]
> napisał(a):
>
> Hello all,
>
> I'm having a small STM32F4 application running on devel
branch of lwip, It includes httpd, sntp, smtp client, and
mqtt client. All is running well until the fifth day, when
mqtt client starts to receive pbuf=NULL and disconnects.
My reconnect routine reconnects it in some short time, but
it receives pbuf=NULL shortly after.
>
> Also later on I noticed in log: memp_malloc: out of
memory in pool TCP_PCB.
> I'm having defined MEMP_NUM_TCP_PCB as 30 and it seems
enough for normal operation, I also upped it to 50, but
ended with the same problem
> In statistics the NUM_TCP_PCB increases and decreases as
it should, but after uptime past 5 days it stays high with
an error flag triggered.
>
> Quite interestingly it happens exactly after 2^32
milliseconds uptime. I tried to keep OpenOCD connected to
start to peek in, but yet I did not manage to keep the
openOCD running for so long without dropping the connection.
>
> Does anyone have any ideas please?
>
> Thanks in advance,
> --
> 731435556
> Adam Baron
> ___
> lwip-users mailing list
> [hidden email]

> https://lists.nongnu.org/mailman/listinfo/lwip-users




--
Pozdrawiam
Tomek

___
lwip-users mailing list
[hidden email] 
https://lists.nongnu.org/mailman/listinfo/lwip-users




-- 
731435556

Adam Baron
___
lwip-users mailing list
[hidden email] 
https://lists.nongnu.org/mailman/listinfo/lwip-users


___
lwip-users mailing list
[hidden email] 
https://lists.nongnu.org/mailman/listinfo/lwip-users




--
731435556
Adam Baron

___
lwip-users mailing list
[hidden email] 
https://lists.nongnu.org/mailman/listinfo/lwip-users 




If you reply to this email, your message will be added to the 
discussion 

[lwip-users] Fwd: Out of memory in PCP_PCB pool after 2^32 milliseconds

[Matthias Paul]

Am 28.05.2021 um 08:58 schrieb vysocan [via lwIP]:

Hello all,

I'm having a small STM32F4 application running on devel branch of 
lwip, It includes httpd, sntp, smtp client, and mqtt client. All is 
running well until the fifth day, when mqtt client starts to receive 
pbuf=NULL and disconnects. My reconnect routine reconnects it in some 
short time, but it receives pbuf=NULL shortly after.


Also later on I noticed in log: memp_malloc: out of memory in pool 
TCP_PCB.
I'm having defined MEMP_NUM_TCP_PCB as 30 and it seems enough for 
normal operation, I also upped it to 50, but ended with the same problem
In statistics the NUM_TCP_PCB increases and decreases as it should, 
but after uptime past 5 days it stays high with an error flag triggered.


Quite interestingly it happens exactly after 2^32 milliseconds uptime. 
I tried to keep OpenOCD connected to start to peek in, but yet I did 
not manage to keep the openOCD running for so long without dropping 
the connection.


Does anyone have any ideas please?

Thanks in advance,
--
731435556
Adam Baron

___
lwip-users mailing list
[hidden email] 
https://lists.nongnu.org/mailman/listinfo/lwip-users 




If you reply to this email, your message will be added to the 
discussion below:
http://lwip.100.n7.nabble.com/Out-of-memory-in-PCP-PCB-pool-after-2-32-milliseconds-tp36460.html 
 

To unsubscribe from lwIP, click here 
.
NAML 
 



Hello Adam,

isn't 2^32 milliseconds actually ~50 days uptime?

Best regards,

Paul

___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users

[lwip-users] Example tcpecho_raw (contrib-2.1.0)

[Matthias Paul]

Hello lwIP users,

questions are about tcpecho_raw example in contrib-2.1.0. The example is 
chosen as an entry point for testing / developing a simple TCP-based 
protocol on a bare-metal microcontroller system.


1. The "enum tcpecho_raw_states" contains states ES_ACCEPTED and 
ES_RECEIVED, which seem to be identical to me. Is there any difference 
in those states other than distinguishing between a client which _did_ 
sent data at least once and a client which never did?


2. If the client closes the connection to the server, "struct 
tcpecho_raw_state.state" switches to ES_CLOSING to allow sending more 
yet unset data to the client. After all data has been sent out to the 
client, the server finally closes the connection. What's the benefit of 
this behaviour? Is it special for this example or is it  a common 
"best-practice" in TCP?


3. The example looks sort of WIP. For example, "struct 
tcpecho_raw_state.retries" is never used. Is there a more complete 
example out there?



Best regards,
Paul


___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users

Re: [nebula-dev] Urgent Nebula bugs to tackle?

[Matthias Paul Scholz]

Hi Laurent,

You might have noticed that I plan to work on the Nebula Notifier a bit to
include some additional features (see above).
Since it has been  contributed to Nebulal by you, Ids like to know what you
think about my ideas?

Is there someting particular that I need to consider regarding the current
state of the widget?
Do you have additional hints or ideas?

Best and thanks,
  MP





Am Do., 8. Apr. 2021 um 11:09 Uhr schrieb Matthias Paul Scholz <
matthias.paul.sch...@gmail.com>:

> Hi Wim,
>
> Am Do., 8. Apr. 2021 um 09:27 Uhr schrieb Wim Jongman <
> wim.jong...@gmail.com>:
>
>>
>> MiniMessage is right where your eyes are _and_ related to the current
>> task (that is how I use it anyway :)
>>
>
>  Just for completeness: I guess one can configure a custom JFace dialog to
> be non-modal, open at the cursor location (which is the default as far as I
> know) and having no buttons.
>
>
>> Yes, very nice. I think these are great additions to Notifier. Notifier
>> was one of Laurents original Opal widgets.
>>
>>
> Ok, so I would throw myself onto the Notifier.
>
> First steps will be
>
> 1. Add a configuration option that allows for opening it on the cursor
> location
> 2. Make it configurable in terms of colors (error, warning, info)
> 3. use 2. for CSS stylability
>
> Do we need some sort of issue/ticket for tracking?
>
> Best,
>   MP
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Urgent Nebula bugs to tackle?

[Matthias Paul Scholz]

Hi Wim,

Am Do., 8. Apr. 2021 um 09:27 Uhr schrieb Wim Jongman :

>
> MiniMessage is right where your eyes are _and_ related to the current task
> (that is how I use it anyway :)
>

 Just for completeness: I guess one can configure a custom JFace dialog to
be non-modal, open at the cursor location (which is the default as far as I
know) and having no buttons.


> Yes, very nice. I think these are great additions to Notifier. Notifier
> was one of Laurents original Opal widgets.
>
>
Ok, so I would throw myself onto the Notifier.

First steps will be

1. Add a configuration option that allows for opening it on the cursor
location
2. Make it configurable in terms of colors (error, warning, info)
3. use 2. for CSS stylability

Do we need some sort of issue/ticket for tracking?

Best,
  MP
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Urgent Nebula bugs to tackle?

[Matthias Paul Scholz]

As a matter of fact, some time ago we have implemented a similar sort of
Notifier in our company that has some useful features like configurable up
time, optional acknowledgeability, sounds and stacking of notifications.
Maybe that would be a good opportunity to enhance the Nebula Notifier with
some of those features now and thus make it even more useful for Users?

Am Do., 8. Apr. 2021 um 08:05 Uhr schrieb Matthias Paul Scholz <
matthias.paul.sch...@gmail.com>:

> Hi Wim,
>
> Tried it.
> Pretty nice. :)
>
> Yet, just out of curiosity: is there a particular reason why you didn't
> use  a custom org.eclipse.jface.dialogs.Dialog internally which takes care
> of all the rendering already? That would make the framework taking care of
> stuff like positioning, themabilty and so on.
>
> I have noticed that there's alreday some similar widget available from
> Nebula, i.e.. the Notifier: https://wiki.eclipse.org/Nebula_Notifier
> Maybe it might be a good idea to enhance that one and make it configurable
> in regard to coloring and the position where it opens instead of creating
> another new wiget?
>
> As a user, I'd prefer to have a smaller set of highly configurable widgets
> instead of a multitude of widgets with some of them doing similar stuff.
>
> What do you think?
>
> Best,
>   MP
>
>
>
> Am Mi., 7. Apr. 2021 um 18:19 Uhr schrieb Wim Jongman <
> wim.jong...@gmail.com>:
>
>> Sometimes we want to give the user a little feedback. "Saved!", "Please
>> wait...", "Loading..", without having to resort to those bulky dialogs.
>>
>> For these use cases, we have invented MiniMessage. MM can display a small
>> message at the current mouse pointer or above a specific control.
>>
>> Just paste the source code below into a UI project package and run as
>> java application. It would be nice if this would make it into Nebula
>>
>> It would be nice if the message box could be
>> round/square/balloon/closable, etc..
>>
>> Let me know what you think.
>>
>> Cheers,
>>
>> Wim
>>
>>
>> /***
>>  * Copyright (c) 2021 Remain Software -  http://remainsoftware.com
>>  * All rights reserved. This program is made available under the terms
>>  * of the Eclipse Public License v1.0 which does not accompanies this
>>  * distribution but is available at
>> http://www.eclipse.org/legal/epl-v10.html
>>  *
>>  * Contributors:
>>  * Wim Jongman - Initial Impl
>>
>>  
>> ***/
>>
>> package com.remainsoftware.common.licensing.util;
>>
>> import org.eclipse.swt.SWT;
>> import org.eclipse.swt.custom.StyledText;
>> import org.eclipse.swt.graphics.Point;
>> import org.eclipse.swt.layout.GridData;
>> import org.eclipse.swt.layout.GridLayout;
>> import org.eclipse.swt.widgets.Composite;
>> import org.eclipse.swt.widgets.Control;
>> import org.eclipse.swt.widgets.Display;
>> import org.eclipse.swt.widgets.Shell;
>> import org.eclipse.ui.PlatformUI;
>>
>> /**
>>  * Shows a mini message for those cases when you want to supply a quick
>> feedback
>>  * to the user without going through the workflow of showing a dialog and
>>  * letting the user press Ok.
>>  * 
>>  * Usage:
>>  * 
>>  * 
>>  * // Show mini message just above cursor position
>>  * MiniMessage.get(2000).open("Saved!");
>>  * // Show mini message just above this control
>>  * MiniMessage(2000).get(1000).above(Control).open("Saved!");
>>  * 
>>  *
>>  * @author Wim Jongman
>>  *
>>  */
>> public class MiniMessage {
>>
>> public static void main(String[] args) {
>> Display display = new Display();
>> MiniMessage.get(2000).openWait("Hello, World!");
>> display.dispose();
>> }
>>
>> /** Error message */
>> public static final String ERROR = "E";
>> /** Info message (default) */
>> public static final String INFO = "I";
>> /** Warning message */
>> public static final String WARNING = "W";
>>
>> private StyledText fStyledText;
>> private Shell fShell;
>> private int fWaitBeforeFade = 0;
>> private Control fControl;
>> private String fType = INFO;
>>
>> /**
>> * Constructs a {@link MiniMessage}.
>> *
>> * @param waitBeforeFade waits n milliseconds before the message starts to
>> fade.
>> *   Fading itse

Re: [nebula-dev] Urgent Nebula bugs to tackle?

[Matthias Paul Scholz]

 message after for example
> the
> * createPartControl method in a view has finished.
> *
> * Must be called from the UI thread.
> *
> * @param text the text to show as the mini message.
> *
> * @see #open(String)
> * @see #openWait(String)
> */
> public void submit(final String text) {
> Runnable runner = () -> doOpen(text, false);
> Display.getCurrent().asyncExec(runner);
> }
>
> /**
> * Opens the {@link MiniMessage} just above the current cursor position
> showing
> * the passed text. It does not wait until the message has faded.
> *
> * @param text the text to show as the mini message.
> *
> * @see #openWait(String)
> */
> public void open(String text) {
> doOpen(text, false);
> }
>
> private void doOpen(String text, boolean wait) {
> try {
> Display display = Display.getDefault();
> fShell = new Shell(display, SWT.NO_TRIM | SWT.ON_TOP | SWT.NO_FOCUS);
> GridLayout gridLayout = new GridLayout(1, false);
> gridLayout.marginWidth = 1;
> gridLayout.marginHeight = 1;
> gridLayout.verticalSpacing = 0;
> gridLayout.horizontalSpacing = 0;
> createContents(fShell, SWT.NONE);
> setText(text);
> Control focusControl = display.getFocusControl();
> fShell.setLayout(gridLayout);
> fShell.pack();
> fShell.setLocation(getLocation());
> fShell.open();
> fShell.layout();
> if (focusControl != null) {
> focusControl.forceFocus();
> }
> Thread thread = new Thread(new Fader(fWaitBeforeFade));
> thread.run();
> while (wait && !fShell.isDisposed()) {
> if (!display.readAndDispatch()) {
> display.sleep();
> }
> }
> } catch (Exception e) {
> e.printStackTrace();
> }
> }
>
> private Point getLocation() {
> if (fControl == null || fControl.isDisposed() || fControl.getParent() ==
> null) {
> Display display = Display.getDefault();
> return display.getCursorLocation();
> }
> return fControl.getParent().toDisplay(
> fControl.getLocation().x + (fControl.getSize().x / 2) -
> (fShell.getSize().x / 2),
> fControl.getLocation().y - fControl.getSize().y - 10);
> }
>
> private void setText(String string) {
> fStyledText.setText(string);
> }
>
> /**
> * Create the composite.
> *
> * @param parent
> * @param style
> */
> private void createContents(Composite parent, int style) {
> GridLayout gridLayout = new GridLayout();
> gridLayout.marginWidth = 9;
> gridLayout.marginHeight = 9;
> parent.setLayout(gridLayout);
> fStyledText = new StyledText(parent, SWT.BORDER);
> fStyledText.setLayoutData(new GridData(SWT.FILL, SWT.FILL, true, true, 1,
> 1));
> fStyledText.setEditable(false);
> fStyledText.setEnabled(false);
> if (ERROR.equals(fType)) {
>
> fStyledText.setBackground(parent.getDisplay().getSystemColor(SWT.COLOR_DARK_RED));
>
> fStyledText.setForeground(parent.getDisplay().getSystemColor(SWT.COLOR_WHITE));
> }
> if (WARNING.equals(fType)) {
>
> fStyledText.setBackground(parent.getDisplay().getSystemColor(SWT.COLOR_DARK_YELLOW));
>
> fStyledText.setForeground(parent.getDisplay().getSystemColor(SWT.COLOR_WHITE));
> } else {
>
> fStyledText.setBackground(parent.getDisplay().getSystemColor(SWT.COLOR_DARK_GREEN));
>
> fStyledText.setForeground(parent.getDisplay().getSystemColor(SWT.COLOR_WHITE));
> }
> }
>
> private class Fader implements Runnable {
> int fAlpha = 255;
> private int fTimerWait = 10;
> private int fWaitBeforeFade = 0;
>
> public Fader(int waitBeforeFade) {
> this.fWaitBeforeFade = waitBeforeFade;
> }
>
> @Override
> public void run() {
> if (fWaitBeforeFade > 0) {
> fShell.getDisplay().timerExec(fWaitBeforeFade, this);
> fWaitBeforeFade = 0;
> } else if (fAlpha <= 5) {
> fShell.dispose();
> } else {
> fAlpha -= 5;
> if (fAlpha < 255) {
> fShell.setAlpha(fAlpha);
> }
> fShell.getDisplay().timerExec(fTimerWait, this);
> }
> }
> }
>
> /**
> * Sets the type. If the type is not any of the valid values then
> * {@link MiniMessage#INFO} will be assumed.
> *
> * @param pType
> * @return this object for chaining
> *
> * @see #ERROR
> * @see #WARNING
> * @see #INFO
> */
> public MiniMessage setType(String pType) {
> fType = pType;
> return this;
> }
> }
>
>
> On Wed, Apr 7, 2021 at 5:16 PM Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
>> Hi Wim,
>>
>> Sounds interesting. :)
>> Tell me more ...
>>
>> Best,
>>   MP
>>
>> Wim Jongman  schrieb am Mi., 7. Apr. 2021, 12:36:
>>
>>> Hey Matthias,
>>>
>>> How about a shiny new widget. I have a prototype of a new widget that we
>>> already use internally. It is very useful but primitive and I think

Re: [nebula-dev] Urgent Nebula bugs to tackle?

[Matthias Paul Scholz]

Hi Wim,

Sounds interesting. :)
Tell me more ...

Best,
  MP

Wim Jongman  schrieb am Mi., 7. Apr. 2021, 12:36:

> Hey Matthias,
>
> How about a shiny new widget. I have a prototype of a new widget that we
> already use internally. It is very useful but primitive and I think you can
> make a great widget out of it.
>
> WDYT?
>
> Cheers,
>
> Wim
>
> On Wed, Apr 7, 2021 at 8:13 AM Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
>> Hi Wim and Laurent,
>>
>> Are there any urgent Nebula bugs that needs particular attention?
>>
>> I'd like to give back something to the project and maybe you could point
>> me to something that has high priority here.
>>
>> How  about https://bugs.eclipse.org/bugs/show_bug.cgi?id=572568, for
>> instance?
>>
>> Best,
>>   MP
>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

[nebula-dev] Urgent Nebula bugs to tackle?

[Matthias Paul Scholz]

Hi Wim and Laurent,

Are there any urgent Nebula bugs that needs particular attention?

I'd like to give back something to the project and maybe you could point me
to something that has high priority here.

How  about https://bugs.eclipse.org/bugs/show_bug.cgi?id=572568, for
instance?

Best,
  MP
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Which formatter to use for Nebula sources?

[Matthias Paul Scholz]

Ah, I see.
So we should reformat the code in question with the standard formatter and
merge it into master to avoid future confusion.

Please drop me a note in case you have not done it already, then I could
tackle that.

Best,
  MP



Am Di., 6. Apr. 2021 um 22:25 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Matthias,
>
> I think I'm responsible : I did not change the formatter, and I used my
> company's one :(
>
> Sorry for that, I've changed and it will not happen again.
>
> Cheers,
>
> Laurent
>
>
>
> Le mar. 6 avr. 2021 à 16:42, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> a écrit :
>
>> Hi Wim,
>>
>> It's org.eclipse.nebula.widgets.cdatetime: when formatting the
>> org.eclipse.nebula.widgets.cdatetime.DatePicker Java source file in the
>> Eclipse IDE (version Eclipse 2020-12) without changing any code, the
>> intendation spaces of the original master file get all replaced by tabs.
>> Tabs for intendation is the default in the "Eclipse [in-built]" formatter.
>>
>> Best,
>>   MP
>>
>> Am Di., 6. Apr. 2021 um 16:01 Uhr schrieb Wim Jongman <
>> wim.jong...@gmail.com>:
>>
>>> Hey Matthias,
>>>
>>> The formatting rules should be in the project settings. What project is
>>> showing issues?
>>>
>>> Cheers,
>>>
>>> Wim
>>>
>>>
>>> On Tue, Apr 6, 2021 at 3:01 PM Matthias Paul Scholz <
>>> matthias.paul.sch...@gmail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> When pushing new changes to my fork of the Nebula project sources, I
>>>> ran into some merge conflicts that arised from formatting changes only.
>>>>
>>>> However, I did use the Eclipse Java formatter in-built into the Eclipse
>>>> 2020-12 version of the IDE.
>>>>
>>>> Is there any other formatter that must be used when editing the nebula
>>>> sources in order to avoid formatting changes?
>>>>
>>>> Best,
>>>>   MP
>>>> ___
>>>> nebula-dev mailing list
>>>> nebula-dev@eclipse.org
>>>> To unsubscribe from this list, visit
>>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>>
>>> ___
>>> nebula-dev mailing list
>>> nebula-dev@eclipse.org
>>> To unsubscribe from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Which formatter to use for Nebula sources?

[Matthias Paul Scholz]

Hi Wim,

It's org.eclipse.nebula.widgets.cdatetime: when formatting the
org.eclipse.nebula.widgets.cdatetime.DatePicker Java source file in the
Eclipse IDE (version Eclipse 2020-12) without changing any code, the
intendation spaces of the original master file get all replaced by tabs.
Tabs for intendation is the default in the "Eclipse [in-built]" formatter.

Best,
  MP

Am Di., 6. Apr. 2021 um 16:01 Uhr schrieb Wim Jongman :

> Hey Matthias,
>
> The formatting rules should be in the project settings. What project is
> showing issues?
>
> Cheers,
>
> Wim
>
>
> On Tue, Apr 6, 2021 at 3:01 PM Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
>> Hi all,
>>
>> When pushing new changes to my fork of the Nebula project sources, I ran
>> into some merge conflicts that arised from formatting changes only.
>>
>> However, I did use the Eclipse Java formatter in-built into the Eclipse
>> 2020-12 version of the IDE.
>>
>> Is there any other formatter that must be used when editing the nebula
>> sources in order to avoid formatting changes?
>>
>> Best,
>>   MP
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

[nebula-dev] Which formatter to use for Nebula sources?

[Matthias Paul Scholz]

Hi all,

When pushing new changes to my fork of the Nebula project sources, I ran
into some merge conflicts that arised from formatting changes only.

However, I did use the Eclipse Java formatter in-built into the Eclipse
2020-12 version of the IDE.

Is there any other formatter that must be used when editing the nebula
sources in order to avoid formatting changes?

Best,
  MP
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] CDateTime: how to CSS style the toolbar of the date picker?

[Matthias Paul Scholz]

Thanks Laurent!

Here we go: https://bugs.eclipse.org/bugs/show_bug.cgi?id=572033

Best,
  MP

Am Mi., 17. März 2021 um 13:51 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Matthias,
>
> Yes, everything is possible for the Nebula Commiters ;)
>
> Please fill a bug :
> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Nebula
>
> I'll work on this topic this week
>
> Thank you for your feedback,
>
> Laurent
>
> Le mer. 17 mars 2021 à 08:40, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> a écrit :
>
>> Hi all,
>>
>> Thanks to the efforts of Laurent, the CDateTime can be styled using the
>> Eclipse CSS styling feature. :)
>>
>> However, there seems to be some gap still: I could not find a possibility
>> to style the colors of the buttons and of the text in the toolbar of the
>> date picker in graphical mode, .i.e. the ok, cancel and "clear" buttons.
>>
>> In particular the  (by default dark gray) "clear" button is almost
>> invisible on a dark background.
>>
>> is is possible to style these buttons somehow?
>>
>> Best and thanks,
>>   MP
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

[nebula-dev] CDateTime: how to CSS style the toolbar of the date picker?

[Matthias Paul Scholz]

Hi all,

Thanks to the efforts of Laurent, the CDateTime can be styled using the
Eclipse CSS styling feature. :)

However, there seems to be some gap still: I could not find a possibility
to style the colors of the buttons and of the text in the toolbar of the
date picker in graphical mode, .i.e. the ok, cancel and "clear" buttons.

In particular the  (by default dark gray) "clear" button is almost
invisible on a dark background.

is is possible to style these buttons somehow?

Best and thanks,
  MP
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] How to receive ok event only in CDateTime widget?

[Matthias Paul Scholz]

Hallo Wim,

Thanks for the proposal.
I am aware of delayed databinding, but you might be interested to hear that
I have found another workaround in the meantime:

I have "slipped in" an intermediate model between the CDateTime instance
and my wrapping widget.
The model is hosted by a class derived from CDateTime that overrides the
postClose() method and registers a KeyAdapter; in both cases, the model's
value is updated with the actual selection.
That way, the wrapping widget can bind to the model's value and fire change
events only when the user commits the popup or enters a key stroke.

This works, but is only a workaround in the end.
It might be more desirable to support that concept natively by the
CDateTime widget itself when it runs in graphical mode.

Another option could have been to register a a selection listener on the
green commit button in the toolbar of the picker; however, that button is
not accessible from "outside" (with good reasons).

What do you think?

Best,
  MP

Am Mo., 15. März 2021 um 18:09 Uhr schrieb Wim Jongman <
wim.jong...@gmail.com>:
>
> Hi Matthias,
>
> Another option is to throttle the selection. Databinding has support for
that.
> [...]
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] How to receive ok event only in CDateTime widget?

[Matthias Paul Scholz]

Hi Wim,

I'm aware that the concept of an edit transction makes sense for the
graphical mode only where the user has some sort of "edit session".
But at least in that case I think there should be such a concept and the
API should provide  a possibility to hook into it.

By the way, I wonder whether both a programmer and the user actually
expects that  the value of the widget gets changed already before she
presses Enter or clicks the green hook.

Best,
  MP


Am Mo., 15. März 2021 um 11:28 Uhr schrieb Wim Jongman <
wim.jong...@gmail.com>:

> Hi Matthias,
>
> It depends on how you use the widget. CDateTime has many faces. When using
> the widget in its simplest form, there is no concept of Enter or OK. So it
> means that databinding has to be different based on the style of the
> widget.
>
> [image: image.png]
>
> Cheers,
>
> Wim
>
>
>
>
> On Mon, Mar 15, 2021 at 10:08 AM Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
>> Hi all,
>>
>> For some years we have used the CDateTime widget in our RCP application
>> which works quite good. :)
>>
>> However, we ran in some troubles lately: to get notion about changes the
>> user made in the widget,  we use the databinding proposed by Henno
>> Vermeulen (see https://www.eclipse.org/forums/index.php/t/172877) that
>> binds our application to a selection event in the widget.
>>
>> There's an issue with that approach, however: it seems that such a
>> selection event is triggered always on each selection inside of the widget.
>> For instance, when the user cycles through the months in the calendar drop
>> down or selects another day, each time a separate selection event is fired.
>> This is inconvenient for us, since we need an event only when the user
>> explicitely commits her changes by selecting the ok button (or pressing
>> enter).
>>
>> This has become crucial for us lately since we have a new use case now
>> where a change in the widget triggers an expensive backend operation - and
>> it is a no go when this happens each time the user changes the month in the
>> calendar drop down ...
>>
>> Is there a possibility to listen for or to bind to ok/enter events on the
>> CDateTime widget only?
>>
>> Thanks,
>>   MP
>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] How to receive ok event only in CDateTime widget?

[Matthias Paul Scholz]

Hi Wim,

Thanks for the quick answer.
Unfortunately, the simple version is no option for us, since our customers
are used to the graphical version for years now already.

A look in the CDateTime sources revealed to me that there isn't a real
concept of an edit transaction in the widget: the value of the widget gets
changed directly on each selection in the picker or input by the user.
There is no model in the widget nor does the  green hook perform any
"commit" of the value to to such a model (as I had expected).

As a result, there is not possibility to hook into that point of lifecycle
with the current state of the CDateTime API. :(
This makes it pretty much unusable for us presently.

I case you agree with me here, I'd propose to refactor the widget with a
decent model-view approach and some hook in the API that allows for
registering for some sort of edit transaction end (I were willing to adopt
that task).

What do you think?

Best,
 MP



Am Mo., 15. März 2021 um 11:28 Uhr schrieb Wim Jongman <
wim.jong...@gmail.com>:

> Hi Matthias,
>
> It depends on how you use the widget. CDateTime has many faces. When using
> the widget in its simplest form, there is no concept of Enter or OK. So it
> means that databinding has to be different based on the style of the
> widget.
>
> [image: image.png]
>
> Cheers,
>
> Wim
>
>
>
>
> On Mon, Mar 15, 2021 at 10:08 AM Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
>> Hi all,
>>
>> For some years we have used the CDateTime widget in our RCP application
>> which works quite good. :)
>>
>> However, we ran in some troubles lately: to get notion about changes the
>> user made in the widget,  we use the databinding proposed by Henno
>> Vermeulen (see https://www.eclipse.org/forums/index.php/t/172877) that
>> binds our application to a selection event in the widget.
>>
>> There's an issue with that approach, however: it seems that such a
>> selection event is triggered always on each selection inside of the widget.
>> For instance, when the user cycles through the months in the calendar drop
>> down or selects another day, each time a separate selection event is fired.
>> This is inconvenient for us, since we need an event only when the user
>> explicitely commits her changes by selecting the ok button (or pressing
>> enter).
>>
>> This has become crucial for us lately since we have a new use case now
>> where a change in the widget triggers an expensive backend operation - and
>> it is a no go when this happens each time the user changes the month in the
>> calendar drop down ...
>>
>> Is there a possibility to listen for or to bind to ok/enter events on the
>> CDateTime widget only?
>>
>> Thanks,
>>   MP
>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

[nebula-dev] How to receive ok event only in CDateTime widget?

[Matthias Paul Scholz]

Hi all,

For some years we have used the CDateTime widget in our RCP application
which works quite good. :)

However, we ran in some troubles lately: to get notion about changes the
user made in the widget,  we use the databinding proposed by Henno
Vermeulen (see https://www.eclipse.org/forums/index.php/t/172877) that
binds our application to a selection event in the widget.

There's an issue with that approach, however: it seems that such a
selection event is triggered always on each selection inside of the widget.
For instance, when the user cycles through the months in the calendar drop
down or selects another day, each time a separate selection event is fired.
This is inconvenient for us, since we need an event only when the user
explicitely commits her changes by selecting the ok button (or pressing
enter).

This has become crucial for us lately since we have a new use case now
where a change in the widget triggers an expensive backend operation - and
it is a no go when this happens each time the user changes the month in the
calendar drop down ...

Is there a possibility to listen for or to bind to ok/enter events on the
CDateTime widget only?

Thanks,
  MP
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] CDateTime: strange behavior on mouse wheel action

[Matthias Paul Scholz]

Hi Laurent,

I have filed a bug report:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=566219

Thanks,
  MP


Am Mi., 19. Aug. 2020 um 18:44 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Matthias,
>
> Well, it sounds like a bug :'(
>
> Can you please fill a bug, I'll have a look then.
>
> Cheers,
>
> Laurent
>
> Le mer. 19 août 2020 à 11:27, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> a écrit :
>
>> Hi,
>>
>> I have noticed an (in my opinion strange)  behavior of the CDateTime
>> widget on Windows when using the mouse wheel:
>>
>> On a view with multiple widgets, one of the them a CDateTime widget, I
>> focus some other widget and subsequently move the mouse over the CDateTime
>> widget (without focussing it); when I now use the mouse wheel, some date is
>> set to the widget.
>>
>> This is not only confusing but also dangerous since the user might
>> accidentally set a date without  having intended it - instead, she wanted
>> to to scroll in the view without changing or setting the date that is
>> associated to the CDateTime widget instance.
>>
>> In the CDateTime source code, there is a listener registered indeed that
>> accepts mouse wheel events and changes the value.
>>
>> Is the behavior above intended?
>> Is there a possibility to switch it off by a client of the widget (I
>> didn't find one)?
>>
>> Best,
>>   MP
>>
>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

[nebula-dev] CDateTime: strange behavior on mouse wheel action

[Matthias Paul Scholz]

Hi,

I have noticed an (in my opinion strange)  behavior of the CDateTime widget
on Windows when using the mouse wheel:

On a view with multiple widgets, one of the them a CDateTime widget, I
focus some other widget and subsequently move the mouse over the CDateTime
widget (without focussing it); when I now use the mouse wheel, some date is
set to the widget.

This is not only confusing but also dangerous since the user might
accidentally set a date without  having intended it - instead, she wanted
to to scroll in the view without changing or setting the date that is
associated to the CDateTime widget instance.

In the CDateTime source code, there is a listener registered indeed that
accepts mouse wheel events and changes the value.

Is the behavior above intended?
Is there a possibility to switch it off by a client of the widget (I didn't
find one)?

Best,
  MP
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] NullPointerException with CDateTime (new in 2.4)

[Matthias Paul Scholz]

Hi Lauren,

You are pretty productive indeed!



Am Do., 23. Juli 2020 um 13:11 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Matthias
>
> The unit tests have been written. The complicated part was the integration
> of the CSS Engine in jUnit test classes, but it is ok now ;)
> I also discovered a subtle bug that is now fixed.
>
> @Wim Jongman  is it possible to release a V2.4.2
> please ?
>
> Have a nice day,
>
> Laurent
>
> Le mar. 21 juil. 2020 à 17:11, Laurent Caron  a
> écrit :
>
>> Hi Matthias
>>
>> Very good news 
>> Wim, is it possible to create another minor release of Nebula ?
>>
>> Have a nice day,
>>
>> Laurent
>>
>> Le mar. 21 juil. 2020 à 16:49, Matthias Paul Scholz <
>> matthias.paul.sch...@gmail.com> a écrit :
>>
>>> Hi Laurent,
>>>
>>> With the snapshot of this morning (202007201259), I haven't encountered
>>> any of the exceptions above any more. :)
>>>
>>> Thanks and best,
>>>   MP
>>>
>>> Am Mo., 20. Juli 2020 um 14:59 Uhr schrieb Laurent Caron <
>>> laurent.ca...@gmail.com>:
>>>
>>>> Hi matthias,
>>>>
>>>> First of all I would like to apologize for these regressions. This NPE
>>>> is fixed, I hope it is the last one.
>>>>
>>>> Concerning unit tests, you are totally right. I am a lazy guy, and I
>>>> merged the evolutions (on an existing widget) without creating associated
>>>> tests. It is not professional.
>>>> I've created a bug entry (
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=565363) and I'll work on
>>>> it.
>>>>
>>>> Thank you for your feedback,
>>>>
>>>> Laurent
>>>>
>>>> Le lun. 20 juil. 2020 à 10:11, Matthias Paul Scholz <
>>>> matthias.paul.sch...@gmail.com> a écrit :
>>>>
>>>>> Hi Laurent,
>>>>>
>>>>> Thanks for the quick reply.
>>>>> I've tested the latest repository snapshot (qualifier 202007171729):
>>>>>
>>>>> 'cdt-picker-active-day-color' works now, but I still get the same NPE
>>>>> when configuring 'cdt-picker-color':
>>>>>
>>>>> java.lang.NullPointerException
>>>>> at
>>>>> org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerForegroundColor(CDateTime.java:2300)
>>>>> at
>>>>> org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:66)
>>>>> at
>>>>> org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)
>>>>>
>>>>> The CDateTime is constructed as
>>>>>
>>>>> new CDateTime(parent, getStyle() | CDT.DROP_DOWN
>>>>>     | CDT.DATE_MEDIUM | CDT.TIME_MEDIUM | CDT.CLOCK_DISCRETE);
>>>>>
>>>>> I wonder whether it wouldn't be helpful to have a series of unit tests
>>>>> here for the css properties(if possible) instead of testing them  with an
>>>>> RCP application on a customized targetplatform (which is somewhat time
>>>>> consuming).
>>>>>
>>>>> Best,
>>>>>  MP
>>>>>
>>>>> Am Fr., 17. Juli 2020 um 19:04 Uhr schrieb Laurent Caron <
>>>>> laurent.ca...@gmail.com>:
>>>>>
>>>>>> Hi Matthias,
>>>>>>
>>>>>> Thank you for your feedback, I think we're getting close (and I'm
>>>>>> very sorry for the bugs, I need holidays).
>>>>>> I've merged my PR, so I think you can give a try to the next snapshot.
>>>>>>
>>>>>> Cheers,
>>>>>> Laurent
>>>>>>
>>>>>> Le ven. 17 juil. 2020 à 16:49, Matthias Paul Scholz <
>>>>>> matthias.paul.sch...@gmail.com> a écrit :
>>>>>>
>>>>>>> I have tested the nebula snapshot from two hours ago (the one
>>>>>>> the gives me qualifiers ending with '202007152209') and configured all 
>>>>>>> the
>>>>>>> CSS color properties for CDateTime listed in the doc (
>>>>>>> https://wiki.eclipse.org/Nebula_CSS_CDateTime).
>>>>>>>
>>>>>>> The only CSS property that still gives rise to a
>>>>>>> NullPointerException w

Re: [nebula-dev] NullPointerException with CDateTime (new in 2.4)

[Matthias Paul Scholz]

Hi Laurent,

With the snapshot of this morning (202007201259), I haven't encountered any
of the exceptions above any more. :)

Thanks and best,
  MP

Am Mo., 20. Juli 2020 um 14:59 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi matthias,
>
> First of all I would like to apologize for these regressions. This NPE is
> fixed, I hope it is the last one.
>
> Concerning unit tests, you are totally right. I am a lazy guy, and I
> merged the evolutions (on an existing widget) without creating associated
> tests. It is not professional.
> I've created a bug entry (
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=565363) and I'll work on it.
>
> Thank you for your feedback,
>
> Laurent
>
> Le lun. 20 juil. 2020 à 10:11, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> a écrit :
>
>> Hi Laurent,
>>
>> Thanks for the quick reply.
>> I've tested the latest repository snapshot (qualifier 202007171729):
>>
>> 'cdt-picker-active-day-color' works now, but I still get the same NPE
>> when configuring 'cdt-picker-color':
>>
>> java.lang.NullPointerException
>> at
>> org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerForegroundColor(CDateTime.java:2300)
>> at
>> org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:66)
>> at
>> org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)
>>
>> The CDateTime is constructed as
>>
>> new CDateTime(parent, getStyle() | CDT.DROP_DOWN
>> | CDT.DATE_MEDIUM | CDT.TIME_MEDIUM | CDT.CLOCK_DISCRETE);
>>
>> I wonder whether it wouldn't be helpful to have a series of unit tests
>> here for the css properties(if possible) instead of testing them  with an
>> RCP application on a customized targetplatform (which is somewhat time
>> consuming).
>>
>> Best,
>>  MP
>>
>> Am Fr., 17. Juli 2020 um 19:04 Uhr schrieb Laurent Caron <
>> laurent.ca...@gmail.com>:
>>
>>> Hi Matthias,
>>>
>>> Thank you for your feedback, I think we're getting close (and I'm very
>>> sorry for the bugs, I need holidays).
>>> I've merged my PR, so I think you can give a try to the next snapshot.
>>>
>>> Cheers,
>>> Laurent
>>>
>>> Le ven. 17 juil. 2020 à 16:49, Matthias Paul Scholz <
>>> matthias.paul.sch...@gmail.com> a écrit :
>>>
>>>> I have tested the nebula snapshot from two hours ago (the one the gives
>>>> me qualifiers ending with '202007152209') and configured all the CSS color
>>>> properties for CDateTime listed in the doc (
>>>> https://wiki.eclipse.org/Nebula_CSS_CDateTime).
>>>>
>>>> The only CSS property that still gives rise to a NullPointerException
>>>> when CDT.DROP_DONE is configured is 'cdt-picker-color' :
>>>>
>>>> java.lang.NullPointerException
>>>> at
>>>> org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerForegroundColor(CDateTime.java:2300)
>>>> at
>>>> org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:66)
>>>> at
>>>> org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)
>>>> at
>>>> org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyStyleDeclaration(AbstractCSSEngine.java:536)
>>>>
>>>> Besides, configuring 'cdt-picker-active-day-color' does not seem to
>>>> have any effect (I take it that the "active day" is the one set in the
>>>> widget?).
>>>>
>>>> Thanks,
>>>>MP
>>>>
>>>>
>>>>
>>>> Am Do., 16. Juli 2020 um 09:45 Uhr schrieb Wim Jongman <
>>>> wim.jong...@gmail.com>:
>>>>
>>>>> The latest snapshot is available 10 minutes after every commit.
>>>>>
>>>>> http://download.eclipse.org/nebula/snapshot
>>>>>
>>>>> from
>>>>>
>>>>> https://www.eclipse.org/nebula/downloads.php
>>>>>
>>>>>
>>>>> On Thu, Jul 16, 2020 at 9:31 AM Matthias Paul Scholz <
>>>>> matthias.paul.sch...@gmail.com> wrote:
>>>>>
>>>>>> Why, certainly.
>>>>>> Just drop me a note when it's available.
>>>>>>
>>>>>> Am Do., 16. Juli 2020 um 09:21 Uhr schrieb Wim Jongman 

Re: [nebula-dev] NullPointerException with CDateTime (new in 2.4)

[Matthias Paul Scholz]

Hi Laurent,

Thanks for the quick reply.
I've tested the latest repository snapshot (qualifier 202007171729):

'cdt-picker-active-day-color' works now, but I still get the same NPE when
configuring 'cdt-picker-color':

java.lang.NullPointerException
at
org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerForegroundColor(CDateTime.java:2300)
at
org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:66)
at
org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)

The CDateTime is constructed as

new CDateTime(parent, getStyle() | CDT.DROP_DOWN
| CDT.DATE_MEDIUM | CDT.TIME_MEDIUM | CDT.CLOCK_DISCRETE);

I wonder whether it wouldn't be helpful to have a series of unit tests here
for the css properties(if possible) instead of testing them  with an
RCP application on a customized targetplatform (which is somewhat time
consuming).

Best,
 MP

Am Fr., 17. Juli 2020 um 19:04 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Matthias,
>
> Thank you for your feedback, I think we're getting close (and I'm very
> sorry for the bugs, I need holidays).
> I've merged my PR, so I think you can give a try to the next snapshot.
>
> Cheers,
> Laurent
>
> Le ven. 17 juil. 2020 à 16:49, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> a écrit :
>
>> I have tested the nebula snapshot from two hours ago (the one the gives
>> me qualifiers ending with '202007152209') and configured all the CSS color
>> properties for CDateTime listed in the doc (
>> https://wiki.eclipse.org/Nebula_CSS_CDateTime).
>>
>> The only CSS property that still gives rise to a NullPointerException
>> when CDT.DROP_DONE is configured is 'cdt-picker-color' :
>>
>> java.lang.NullPointerException
>> at
>> org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerForegroundColor(CDateTime.java:2300)
>> at
>> org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:66)
>> at
>> org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)
>> at
>> org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyStyleDeclaration(AbstractCSSEngine.java:536)
>>
>> Besides, configuring 'cdt-picker-active-day-color' does not seem to have
>> any effect (I take it that the "active day" is the one set in the widget?).
>>
>> Thanks,
>>MP
>>
>>
>>
>> Am Do., 16. Juli 2020 um 09:45 Uhr schrieb Wim Jongman <
>> wim.jong...@gmail.com>:
>>
>>> The latest snapshot is available 10 minutes after every commit.
>>>
>>> http://download.eclipse.org/nebula/snapshot
>>>
>>> from
>>>
>>> https://www.eclipse.org/nebula/downloads.php
>>>
>>>
>>> On Thu, Jul 16, 2020 at 9:31 AM Matthias Paul Scholz <
>>> matthias.paul.sch...@gmail.com> wrote:
>>>
>>>> Why, certainly.
>>>> Just drop me a note when it's available.
>>>>
>>>> Am Do., 16. Juli 2020 um 09:21 Uhr schrieb Wim Jongman <
>>>> wim.jong...@gmail.com>:
>>>>
>>>>> Sure! Matthias, maybe you can take the snapshot release for a spin?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Wim
>>>>>
>>>>> On Wed, Jul 15, 2020 at 11:16 PM Laurent Caron <
>>>>> laurent.ca...@gmail.com> wrote:
>>>>>
>>>>>> Good Evening,
>>>>>>
>>>>>> I'm sorry for the problems found. I've created a bug (
>>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=565249) and fixed the
>>>>>> exception.
>>>>>>
>>>>>> Wim, do you think we can create a V2.4.2 release ?
>>>>>>
>>>>>> Matthias, for the CLOCK_DISCRETE problem, can you please fill a bug (
>>>>>> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Nebula) and post
>>>>>> a sample code.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Laurent
>>>>>>
>>>>>> Le mer. 15 juil. 2020 à 16:42, Matthias Paul Scholz <
>>>>>> matthias.paul.sch...@gmail.com> a écrit :
>>>>>>
>>>>>>> Hi, thanks for the patch release (2.4.1).
>>>>>>>
>>>>>>> I tried it with our application.
>>>>>>> Good news: the NPE in the CDateTime widget from 2.4.0 is fixed

Re: [nebula-dev] NullPointerException with CDateTime (new in 2.4)

[Matthias Paul Scholz]

I have tested the nebula snapshot from two hours ago (the one the gives me
qualifiers ending with '202007152209') and configured all the CSS color
properties for CDateTime listed in the doc (
https://wiki.eclipse.org/Nebula_CSS_CDateTime).

The only CSS property that still gives rise to a NullPointerException when
CDT.DROP_DONE is configured is 'cdt-picker-color' :

java.lang.NullPointerException
at
org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerForegroundColor(CDateTime.java:2300)
at
org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:66)
at
org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)
at
org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyStyleDeclaration(AbstractCSSEngine.java:536)

Besides, configuring 'cdt-picker-active-day-color' does not seem to have
any effect (I take it that the "active day" is the one set in the widget?).

Thanks,
   MP



Am Do., 16. Juli 2020 um 09:45 Uhr schrieb Wim Jongman <
wim.jong...@gmail.com>:

> The latest snapshot is available 10 minutes after every commit.
>
> http://download.eclipse.org/nebula/snapshot
>
> from
>
> https://www.eclipse.org/nebula/downloads.php
>
>
> On Thu, Jul 16, 2020 at 9:31 AM Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
>> Why, certainly.
>> Just drop me a note when it's available.
>>
>> Am Do., 16. Juli 2020 um 09:21 Uhr schrieb Wim Jongman <
>> wim.jong...@gmail.com>:
>>
>>> Sure! Matthias, maybe you can take the snapshot release for a spin?
>>>
>>> Cheers,
>>>
>>> Wim
>>>
>>> On Wed, Jul 15, 2020 at 11:16 PM Laurent Caron 
>>> wrote:
>>>
>>>> Good Evening,
>>>>
>>>> I'm sorry for the problems found. I've created a bug (
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=565249) and fixed the
>>>> exception.
>>>>
>>>> Wim, do you think we can create a V2.4.2 release ?
>>>>
>>>> Matthias, for the CLOCK_DISCRETE problem, can you please fill a bug (
>>>> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Nebula) and post a
>>>> sample code.
>>>>
>>>> Regards,
>>>>
>>>> Laurent
>>>>
>>>> Le mer. 15 juil. 2020 à 16:42, Matthias Paul Scholz <
>>>> matthias.paul.sch...@gmail.com> a écrit :
>>>>
>>>>> Hi, thanks for the patch release (2.4.1).
>>>>>
>>>>> I tried it with our application.
>>>>> Good news: the NPE in the CDateTime widget from 2.4.0 is fixed.
>>>>> Bad news: another NPE occurs  in the CDateTime widget now when
>>>>> configuring the fore ground color for the minutes in the picker (using the
>>>>> CSS-property "cdt-picker-minutes-color"):
>>>>>
>>>>> java.lang.NullPointerException: null
>>>>> at
>>>>> org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerMinutesColor(CDateTime.java:2404)
>>>>> ~[org.eclipse.nebula.widgets.cdatetime_1.4.0.202007101949.jar:na]
>>>>> at
>>>>> org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:100)
>>>>> ~[org.eclipse.nebula.widgets.cdatetime.css_1.4.0.202007101949.jar:na]
>>>>> at
>>>>> org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)
>>>>> ~[org.eclipse.e4.ui.css.core_0.12.700.v20190513-2118.jar:na]
>>>>>
>>>>> Looks like there are usages of the picker instance still in the class
>>>>> that are not checked for null...
>>>>>
>>>>> Best,
>>>>>   MP
>>>>>
>>>>> P.S. Besides, should setting CDT.CLOCK_DISCRETE flag in the CDateTime
>>>>> widget work in 2.4.1?
>>>>> Regardless whether it is set in the constructor or not, I always get
>>>>> the analog clock.
>>>>>
>>>>> Am Do., 9. Juli 2020 um 22:58 Uhr schrieb Wim Jongman <
>>>>> wim.jong...@gmail.com>:
>>>>>
>>>>>> Hi Matthias,
>>>>>>
>>>>>> We (Laurent) already fixed this. I will make an intermediate 2.4.1
>>>>>> release for this issue ASAP.
>>>>>>
>>>>>> In the meantime you may use the snapshot build.
>>>>>>
>>>>>> Cheers,

Re: [nebula-dev] NullPointerException with CDateTime (new in 2.4)

[Matthias Paul Scholz]

Why, certainly.
Just drop me a note when it's available.

Am Do., 16. Juli 2020 um 09:21 Uhr schrieb Wim Jongman <
wim.jong...@gmail.com>:

> Sure! Matthias, maybe you can take the snapshot release for a spin?
>
> Cheers,
>
> Wim
>
> On Wed, Jul 15, 2020 at 11:16 PM Laurent Caron 
> wrote:
>
>> Good Evening,
>>
>> I'm sorry for the problems found. I've created a bug (
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=565249) and fixed the
>> exception.
>>
>> Wim, do you think we can create a V2.4.2 release ?
>>
>> Matthias, for the CLOCK_DISCRETE problem, can you please fill a bug (
>> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Nebula) and post a
>> sample code.
>>
>> Regards,
>>
>> Laurent
>>
>> Le mer. 15 juil. 2020 à 16:42, Matthias Paul Scholz <
>> matthias.paul.sch...@gmail.com> a écrit :
>>
>>> Hi, thanks for the patch release (2.4.1).
>>>
>>> I tried it with our application.
>>> Good news: the NPE in the CDateTime widget from 2.4.0 is fixed.
>>> Bad news: another NPE occurs  in the CDateTime widget now when
>>> configuring the fore ground color for the minutes in the picker (using the
>>> CSS-property "cdt-picker-minutes-color"):
>>>
>>> java.lang.NullPointerException: null
>>> at
>>> org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerMinutesColor(CDateTime.java:2404)
>>> ~[org.eclipse.nebula.widgets.cdatetime_1.4.0.202007101949.jar:na]
>>> at
>>> org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:100)
>>> ~[org.eclipse.nebula.widgets.cdatetime.css_1.4.0.202007101949.jar:na]
>>> at
>>> org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)
>>> ~[org.eclipse.e4.ui.css.core_0.12.700.v20190513-2118.jar:na]
>>>
>>> Looks like there are usages of the picker instance still in the class
>>> that are not checked for null...
>>>
>>> Best,
>>>   MP
>>>
>>> P.S. Besides, should setting CDT.CLOCK_DISCRETE flag in the CDateTime
>>> widget work in 2.4.1?
>>> Regardless whether it is set in the constructor or not, I always get the
>>> analog clock.
>>>
>>> Am Do., 9. Juli 2020 um 22:58 Uhr schrieb Wim Jongman <
>>> wim.jong...@gmail.com>:
>>>
>>>> Hi Matthias,
>>>>
>>>> We (Laurent) already fixed this. I will make an intermediate 2.4.1
>>>> release for this issue ASAP.
>>>>
>>>> In the meantime you may use the snapshot build.
>>>>
>>>> Cheers,
>>>>
>>>> Wim
>>>>
>>>> On Thu, Jul 9, 2020, 4:51 PM Matthias Paul Scholz <
>>>> matthias.paul.sch...@gmail.com> wrote:
>>>>
>>>>> Thanks for the new release and in particular  the theming support for
>>>>> various widgets!
>>>>>
>>>>> Sadly, when switching to the 2.4 in our application
>>>>> (without changing any code)  I instantly ran into a NullPointerException
>>>>> in the CDateTime widget.
>>>>>
>>>>> Creating a CDateTime with
>>>>>
>>>>> new CDateTime(parent, getStyle() | CDT.DROP_DOWN  | CDT.DATE_MEDIUM |
>>>>> CDT.TIME_MEDIUM | CDT.CLOCK_DISCRETE);
>>>>>
>>>>> (which worked with 2.3) led to
>>>>>
>>>>>  java.lang.NullPointerException
>>>>> at
>>>>> org.eclipse.nebula.widgets.cdatetime.CDateTime.setBackground(CDateTime.java:2245)
>>>>> at
>>>>> org.eclipse.e4.ui.css.swt.helpers.CSSSWTColorHelper.setBackground(CSSSWTColorHelper.java:360)
>>>>> at
>>>>> org.eclipse.e4.ui.css.swt.properties.css2.CSSPropertyBackgroundSWTHandler.applyCSSPropertyBackgroundColor(CSSPropertyBackgroundSWTHandler.java:80)
>>>>>
>>>>> Looks like the picker instance is always null when not using
>>>>> CDT.SIMPLE ...
>>>>>
>>>>> Best,
>>>>>   MP
>>>>> ___
>>>>> nebula-dev mailing list
>>>>> nebula-dev@eclipse.org
>>>>> To unsubscribe from this list, visit
>>>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>>>
>>>> ___
>>>> nebula-dev mailing list
>>>> nebula-dev@eclipse.org
>>>> To unsubscribe from this list, visit
>>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>>
>>> ___
>>> nebula-dev mailing list
>>> nebula-dev@eclipse.org
>>> To unsubscribe from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] NullPointerException with CDateTime (new in 2.4)

[Matthias Paul Scholz]

And there's another NPE when configuring the picker background using the
CSS-property  "cdt-picker-background-color":

java.lang.NullPointerException: null
at
org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerBackgroundColor(CDateTime.java:2314)
~[org.eclipse.nebula.widgets.cdatetime_1.4.0.202007101949.jar:na]
at
org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:62)
~[org.eclipse.nebula.widgets.cdatetime.css_1.4.0.202007101949.jar:na

"pickerPanel" seems to be null here.

Am Mi., 15. Juli 2020 um 16:41 Uhr schrieb Matthias Paul Scholz <
matthias.paul.sch...@gmail.com>:

> Hi, thanks for the patch release (2.4.1).
>
> I tried it with our application.
> Good news: the NPE in the CDateTime widget from 2.4.0 is fixed.
> Bad news: another NPE occurs  in the CDateTime widget now when configuring
> the fore ground color for the minutes in the picker (using the CSS-property
> "cdt-picker-minutes-color"):
>
> java.lang.NullPointerException: null
> at
> org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerMinutesColor(CDateTime.java:2404)
> ~[org.eclipse.nebula.widgets.cdatetime_1.4.0.202007101949.jar:na]
> at
> org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:100)
> ~[org.eclipse.nebula.widgets.cdatetime.css_1.4.0.202007101949.jar:na]
> at
> org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)
> ~[org.eclipse.e4.ui.css.core_0.12.700.v20190513-2118.jar:na]
>
> Looks like there are usages of the picker instance still in the class that
> are not checked for null...
>
> Best,
>   MP
>
> P.S. Besides, should setting CDT.CLOCK_DISCRETE flag in the CDateTime
> widget work in 2.4.1?
> Regardless whether it is set in the constructor or not, I always get the
> analog clock.
>
> Am Do., 9. Juli 2020 um 22:58 Uhr schrieb Wim Jongman <
> wim.jong...@gmail.com>:
>
>> Hi Matthias,
>>
>> We (Laurent) already fixed this. I will make an intermediate 2.4.1
>> release for this issue ASAP.
>>
>> In the meantime you may use the snapshot build.
>>
>> Cheers,
>>
>> Wim
>>
>> On Thu, Jul 9, 2020, 4:51 PM Matthias Paul Scholz <
>> matthias.paul.sch...@gmail.com> wrote:
>>
>>> Thanks for the new release and in particular  the theming support for
>>> various widgets!
>>>
>>> Sadly, when switching to the 2.4 in our application
>>> (without changing any code)  I instantly ran into a NullPointerException
>>> in the CDateTime widget.
>>>
>>> Creating a CDateTime with
>>>
>>> new CDateTime(parent, getStyle() | CDT.DROP_DOWN  | CDT.DATE_MEDIUM |
>>> CDT.TIME_MEDIUM | CDT.CLOCK_DISCRETE);
>>>
>>> (which worked with 2.3) led to
>>>
>>>  java.lang.NullPointerException
>>> at
>>> org.eclipse.nebula.widgets.cdatetime.CDateTime.setBackground(CDateTime.java:2245)
>>> at
>>> org.eclipse.e4.ui.css.swt.helpers.CSSSWTColorHelper.setBackground(CSSSWTColorHelper.java:360)
>>> at
>>> org.eclipse.e4.ui.css.swt.properties.css2.CSSPropertyBackgroundSWTHandler.applyCSSPropertyBackgroundColor(CSSPropertyBackgroundSWTHandler.java:80)
>>>
>>> Looks like the picker instance is always null when not using CDT.SIMPLE
>>> ...
>>>
>>> Best,
>>>   MP
>>> ___
>>> nebula-dev mailing list
>>> nebula-dev@eclipse.org
>>> To unsubscribe from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] NullPointerException with CDateTime (new in 2.4)

[Matthias Paul Scholz]

Hi, thanks for the patch release (2.4.1).

I tried it with our application.
Good news: the NPE in the CDateTime widget from 2.4.0 is fixed.
Bad news: another NPE occurs  in the CDateTime widget now when configuring
the fore ground color for the minutes in the picker (using the CSS-property
"cdt-picker-minutes-color"):

java.lang.NullPointerException: null
at
org.eclipse.nebula.widgets.cdatetime.CDateTime.setPickerMinutesColor(CDateTime.java:2404)
~[org.eclipse.nebula.widgets.cdatetime_1.4.0.202007101949.jar:na]
at
org.eclipse.nebula.widgets.cdatetime.css.CDateTimePropertyHandler.applyCSSProperty(CDateTimePropertyHandler.java:100)
~[org.eclipse.nebula.widgets.cdatetime.css_1.4.0.202007101949.jar:na]
at
org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.applyCSSProperty(AbstractCSSEngine.java:726)
~[org.eclipse.e4.ui.css.core_0.12.700.v20190513-2118.jar:na]

Looks like there are usages of the picker instance still in the class that
are not checked for null...

Best,
  MP

P.S. Besides, should setting CDT.CLOCK_DISCRETE flag in the CDateTime
widget work in 2.4.1?
Regardless whether it is set in the constructor or not, I always get the
analog clock.

Am Do., 9. Juli 2020 um 22:58 Uhr schrieb Wim Jongman :

> Hi Matthias,
>
> We (Laurent) already fixed this. I will make an intermediate 2.4.1 release
> for this issue ASAP.
>
> In the meantime you may use the snapshot build.
>
> Cheers,
>
> Wim
>
> On Thu, Jul 9, 2020, 4:51 PM Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
>> Thanks for the new release and in particular  the theming support for
>> various widgets!
>>
>> Sadly, when switching to the 2.4 in our application (without changing any
>> code)  I instantly ran into a NullPointerException  in the CDateTime widget.
>>
>> Creating a CDateTime with
>>
>> new CDateTime(parent, getStyle() | CDT.DROP_DOWN  | CDT.DATE_MEDIUM |
>> CDT.TIME_MEDIUM | CDT.CLOCK_DISCRETE);
>>
>> (which worked with 2.3) led to
>>
>>  java.lang.NullPointerException
>> at
>> org.eclipse.nebula.widgets.cdatetime.CDateTime.setBackground(CDateTime.java:2245)
>> at
>> org.eclipse.e4.ui.css.swt.helpers.CSSSWTColorHelper.setBackground(CSSSWTColorHelper.java:360)
>> at
>> org.eclipse.e4.ui.css.swt.properties.css2.CSSPropertyBackgroundSWTHandler.applyCSSPropertyBackgroundColor(CSSPropertyBackgroundSWTHandler.java:80)
>>
>> Looks like the picker instance is always null when not using CDT.SIMPLE
>> ...
>>
>> Best,
>>   MP
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

[nebula-dev] NullPointerException with CDateTime (new in 2.4)

[Matthias Paul Scholz]

Thanks for the new release and in particular  the theming support for
various widgets!

Sadly, when switching to the 2.4 in our application (without changing any
code)  I instantly ran into a NullPointerException  in the CDateTime widget.

Creating a CDateTime with

new CDateTime(parent, getStyle() | CDT.DROP_DOWN  | CDT.DATE_MEDIUM |
CDT.TIME_MEDIUM | CDT.CLOCK_DISCRETE);

(which worked with 2.3) led to

 java.lang.NullPointerException
at
org.eclipse.nebula.widgets.cdatetime.CDateTime.setBackground(CDateTime.java:2245)
at
org.eclipse.e4.ui.css.swt.helpers.CSSSWTColorHelper.setBackground(CSSSWTColorHelper.java:360)
at
org.eclipse.e4.ui.css.swt.properties.css2.CSSPropertyBackgroundSWTHandler.applyCSSPropertyBackgroundColor(CSSPropertyBackgroundSWTHandler.java:80)

Looks like the picker instance is always null when not using CDT.SIMPLE ...

Best,
  MP
___
nebula-dev mailing list
nebula-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Theming support in new widgets?

[Matthias Paul Scholz]

Hi Laurent,

So maybe we should also add a separate sample section for the border color
in the UI of *org.eclipse.nebula.widgets.tablecombo.example.e4*?
I could do that in case that's ok for you?

Comprehensive support for customization of the DateTime widget using E4
CSS-based theming would be great indeed.

Best,
  MP


Am So., 1. März 2020 um 17:10 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Matthias
>
> I would like to apologize for my late answer (I was far away from Internet
> ;) )
>
> I'm very happy if you appreciate this work !!
>
> If you want to customize the border color, you have to use the property "
> *tablecombo-border-color*". There was an error in the documentation, it
> is fixed now.
> Here is an example extracted from [1]
>
> TableCombo#two {
>   font: Verdana 11px;
>   background-color: darkred;
>   color: white;
>   tablecombo-show-table-lines: true;
>   tablecombo-show-table-header: true;
>   *tablecombo-border-color: red;*
> }
>
> If I remember well, you wanted also the possibility to custom the "date
> time" widget.
> Is it still ok for you ?
>
> Have a nice day,
>
> Laurent
>
> [1] =
> https://github.com/eclipse/nebula/blob/master/widgets/tablecombo/org.eclipse.nebula.widgets.tablecombo.example.e4/css/default.css
>
>
> Le lun. 24 févr. 2020 à 14:04, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> a écrit :
>
>> Hi Laurent,
>>
>> I am testing you new Table Combo CSS features and so far, your new
>> features and the table combo CSS sample app work fine in my IDE.
>> Great work!
>>
>> One small thing, though:
>> There's  support for setting the border color by a CSS property in
>> the  TableComboPropertyHandler, but none in the sample app nor in the
>> documentation - did I miss something?
>>
>> Best,
>>   MP
>>
>> Am Mo., 24. Feb. 2020 um 13:21 Uhr schrieb Matthias Paul Scholz <
>> matthias.paul.sch...@gmail.com>:
>>
>>> Hi Laurent,
>>>
>>> Thank you.
>>> I will have a look  this week.
>>>
>>> Best,
>>>   MP
>>>
>>> Am Fr., 21. Feb. 2020 um 15:58 Uhr schrieb Laurent Caron <
>>> laurent.ca...@gmail.com>:
>>>
>>>> Hi Matthias
>>>>
>>>> On the latest snap of Nebula you'll find my work on "TableCombo
>>>> Theming".
>>>>
>>>> In order to do so, you just have to use the plugin
>>>> *org.eclipse.nebula.widgets.tablecombo.css* or the feature
>>>> *org.eclipse.nebula.widgets.tablecombo.css.feature*
>>>>
>>>> An e4 sample application called "
>>>> *org.eclipse.nebula.widgets.tablecombo.example.e4*" is available under
>>>> the /widgets/tablecombo directory.
>>>>
>>>> I've created a documentation: please have a look at
>>>> https://wiki.eclipse.org/Nebula_CSS_TableCombo
>>>>
>>>> <https://wiki.eclipse.org/Nebula_CSS_TableCombo>
>>>> You'll notice a little improvement : you can change the color for the
>>>> border of the widget ;)
>>>>
>>>> Have a nice week-end,
>>>>
>>>> Laurent
>>>>
>>>> Le mar. 18 févr. 2020 à 11:19, Matthias Paul Scholz <
>>>> matthias.paul.sch...@gmail.com> a écrit :
>>>>
>>>>> Hi Laurent,
>>>>>
>>>>> Great.
>>>>> Just tell me when you need a test person.
>>>>>
>>>>> Best,
>>>>>   MP
>>>>>
>>>>> Am Mo., 17. Feb. 2020 um 19:28 Uhr schrieb Laurent Caron <
>>>>> laurent.ca...@gmail.com>:
>>>>>
>>>>>> Hi Paul,
>>>>>>
>>>>>> Well, to be honest I have time and I like to improve myself in
>>>>>> subject I'm not good at.
>>>>>>
>>>>>> If you can help me for testing, I can create plugins for TableCombo
>>>>>> and CDateTime that handle css properties.
>>>>>>
>>>>>> If you agree, I'll create entries in Bugzilla and work on it this
>>>>>> week.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Laurent
>>>>>>
>>>>>>
>>>>>> Le lun. 17 févr. 2020 à 17:25, Matthias Paul Scholz <
>>>>>> matthias.paul.sch...@gmail.com> a écrit :
>>>>>>
>>>&

Re: [nebula-dev] Theming support in new widgets?

[Matthias Paul Scholz]

Hi Laurent,

I am testing you new Table Combo CSS features and so far, your new
features and the table combo CSS sample app work fine in my IDE.
Great work!

One small thing, though:
There's  support for setting the border color by a CSS property in
the  TableComboPropertyHandler, but none in the sample app nor in the
documentation - did I miss something?

Best,
  MP

Am Mo., 24. Feb. 2020 um 13:21 Uhr schrieb Matthias Paul Scholz <
matthias.paul.sch...@gmail.com>:

> Hi Laurent,
>
> Thank you.
> I will have a look  this week.
>
> Best,
>   MP
>
> Am Fr., 21. Feb. 2020 um 15:58 Uhr schrieb Laurent Caron <
> laurent.ca...@gmail.com>:
>
>> Hi Matthias
>>
>> On the latest snap of Nebula you'll find my work on "TableCombo Theming".
>>
>> In order to do so, you just have to use the plugin
>> *org.eclipse.nebula.widgets.tablecombo.css* or the feature
>> *org.eclipse.nebula.widgets.tablecombo.css.feature*
>>
>> An e4 sample application called "
>> *org.eclipse.nebula.widgets.tablecombo.example.e4*" is available under
>> the /widgets/tablecombo directory.
>>
>> I've created a documentation: please have a look at
>> https://wiki.eclipse.org/Nebula_CSS_TableCombo
>>
>> <https://wiki.eclipse.org/Nebula_CSS_TableCombo>
>> You'll notice a little improvement : you can change the color for the
>> border of the widget ;)
>>
>> Have a nice week-end,
>>
>> Laurent
>>
>> Le mar. 18 févr. 2020 à 11:19, Matthias Paul Scholz <
>> matthias.paul.sch...@gmail.com> a écrit :
>>
>>> Hi Laurent,
>>>
>>> Great.
>>> Just tell me when you need a test person.
>>>
>>> Best,
>>>   MP
>>>
>>> Am Mo., 17. Feb. 2020 um 19:28 Uhr schrieb Laurent Caron <
>>> laurent.ca...@gmail.com>:
>>>
>>>> Hi Paul,
>>>>
>>>> Well, to be honest I have time and I like to improve myself in subject
>>>> I'm not good at.
>>>>
>>>> If you can help me for testing, I can create plugins for TableCombo and
>>>> CDateTime that handle css properties.
>>>>
>>>> If you agree, I'll create entries in Bugzilla and work on it this week.
>>>>
>>>> Cheers,
>>>>
>>>> Laurent
>>>>
>>>>
>>>> Le lun. 17 févr. 2020 à 17:25, Matthias Paul Scholz <
>>>> matthias.paul.sch...@gmail.com> a écrit :
>>>>
>>>>> Hi Laurent,
>>>>>
>>>>> Merci for the quick response.
>>>>> Indeed, it's E4 theming I was referring too.
>>>>>
>>>>> Nebula widgets we were not able to style satisfyingly were in
>>>>> particular the TableCombo and the CDateTime widget (for the TableCombo the
>>>>> text field border and the button do not seem to be accessible for theming,
>>>>> while with the  CDateTimeWidget more or less the background only can be
>>>>> styled).
>>>>> Yet, I do not ask someone else to fix this, but hope to come up with
>>>>> some support for that in the code base of the widgets by myself.
>>>>>
>>>>> But it would be nice when new widgets came along with the required CSS
>>>>> properties for E4 theming quite from the beginning.
>>>>> If help is welcome here, I'd be willing to lend a hand (however,
>>>>> unfortunately I cannot  promise constant and quick response).
>>>>>
>>>>> Best,
>>>>>   MP
>>>>>
>>>>> Am Mo., 17. Feb. 2020 um 16:30 Uhr schrieb Laurent Caron <
>>>>> laurent.ca...@gmail.com>:
>>>>>
>>>>>> Hi Matthias,
>>>>>>
>>>>>> Thank you for your message. I wrote many new widgets and I have to
>>>>>> admit that I did not take care of this aspect (probably because I'm not
>>>>>> able to work with the Dark Theme of Eclipse or VSCode).
>>>>>>
>>>>>> When you are talking about theming, you're talking about e4 theming,
>>>>>> right ? (like the dark mode in Eclipse)
>>>>>>
>>>>>> Can you tell what widgets cause problem in your application ? Or post
>>>>>> a screenshot if possible ?
>>>>>>
>>>>>> Thank you for your feedback,
>>>>>>
>>>>>> Laurent
>>>>>>
>>>>>>
>>>>>&g

Re: [nebula-dev] Theming support in new widgets?

[Matthias Paul Scholz]

Hi Laurent,

Thank you.
I will have a look  this week.

Best,
  MP

Am Fr., 21. Feb. 2020 um 15:58 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Matthias
>
> On the latest snap of Nebula you'll find my work on "TableCombo Theming".
>
> In order to do so, you just have to use the plugin
> *org.eclipse.nebula.widgets.tablecombo.css* or the feature
> *org.eclipse.nebula.widgets.tablecombo.css.feature*
>
> An e4 sample application called "
> *org.eclipse.nebula.widgets.tablecombo.example.e4*" is available under
> the /widgets/tablecombo directory.
>
> I've created a documentation: please have a look at
> https://wiki.eclipse.org/Nebula_CSS_TableCombo
>
> <https://wiki.eclipse.org/Nebula_CSS_TableCombo>
> You'll notice a little improvement : you can change the color for the
> border of the widget ;)
>
> Have a nice week-end,
>
> Laurent
>
> Le mar. 18 févr. 2020 à 11:19, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> a écrit :
>
>> Hi Laurent,
>>
>> Great.
>> Just tell me when you need a test person.
>>
>> Best,
>>   MP
>>
>> Am Mo., 17. Feb. 2020 um 19:28 Uhr schrieb Laurent Caron <
>> laurent.ca...@gmail.com>:
>>
>>> Hi Paul,
>>>
>>> Well, to be honest I have time and I like to improve myself in subject
>>> I'm not good at.
>>>
>>> If you can help me for testing, I can create plugins for TableCombo and
>>> CDateTime that handle css properties.
>>>
>>> If you agree, I'll create entries in Bugzilla and work on it this week.
>>>
>>> Cheers,
>>>
>>> Laurent
>>>
>>>
>>> Le lun. 17 févr. 2020 à 17:25, Matthias Paul Scholz <
>>> matthias.paul.sch...@gmail.com> a écrit :
>>>
>>>> Hi Laurent,
>>>>
>>>> Merci for the quick response.
>>>> Indeed, it's E4 theming I was referring too.
>>>>
>>>> Nebula widgets we were not able to style satisfyingly were in
>>>> particular the TableCombo and the CDateTime widget (for the TableCombo the
>>>> text field border and the button do not seem to be accessible for theming,
>>>> while with the  CDateTimeWidget more or less the background only can be
>>>> styled).
>>>> Yet, I do not ask someone else to fix this, but hope to come up with
>>>> some support for that in the code base of the widgets by myself.
>>>>
>>>> But it would be nice when new widgets came along with the required CSS
>>>> properties for E4 theming quite from the beginning.
>>>> If help is welcome here, I'd be willing to lend a hand (however,
>>>> unfortunately I cannot  promise constant and quick response).
>>>>
>>>> Best,
>>>>   MP
>>>>
>>>> Am Mo., 17. Feb. 2020 um 16:30 Uhr schrieb Laurent Caron <
>>>> laurent.ca...@gmail.com>:
>>>>
>>>>> Hi Matthias,
>>>>>
>>>>> Thank you for your message. I wrote many new widgets and I have to
>>>>> admit that I did not take care of this aspect (probably because I'm not
>>>>> able to work with the Dark Theme of Eclipse or VSCode).
>>>>>
>>>>> When you are talking about theming, you're talking about e4 theming,
>>>>> right ? (like the dark mode in Eclipse)
>>>>>
>>>>> Can you tell what widgets cause problem in your application ? Or post
>>>>> a screenshot if possible ?
>>>>>
>>>>> Thank you for your feedback,
>>>>>
>>>>> Laurent
>>>>>
>>>>>
>>>>> Le lun. 17 févr. 2020 à 13:50, Matthias Paul Scholz <
>>>>> matthias.paul.sch...@gmail.com> a écrit :
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I see a lot of new widgets being added to our beloved Nebula lately
>>>>>> which is great!
>>>>>> Yet, I wonder whether also support for theming is considered by the
>>>>>> authors when creating the first release versions for them?
>>>>>>
>>>>>> Using a lot of the "classic" Nebula widgets in our RCP application
>>>>>> (that includes theming as a matter of course), we noticed that theming
>>>>>> support is rather sparse for the Nebula widgets so far; in my opinion, 
>>>>>> this
>>>>>> is some sort of 

Re: [nebula-dev] Theming support in new widgets?

[Matthias Paul Scholz]

Hi Laurent,

Great.
Just tell me when you need a test person.

Best,
  MP

Am Mo., 17. Feb. 2020 um 19:28 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Paul,
>
> Well, to be honest I have time and I like to improve myself in subject I'm
> not good at.
>
> If you can help me for testing, I can create plugins for TableCombo and
> CDateTime that handle css properties.
>
> If you agree, I'll create entries in Bugzilla and work on it this week.
>
> Cheers,
>
> Laurent
>
>
> Le lun. 17 févr. 2020 à 17:25, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> a écrit :
>
>> Hi Laurent,
>>
>> Merci for the quick response.
>> Indeed, it's E4 theming I was referring too.
>>
>> Nebula widgets we were not able to style satisfyingly were in particular
>> the TableCombo and the CDateTime widget (for the TableCombo the text field
>> border and the button do not seem to be accessible for theming, while with
>> the  CDateTimeWidget more or less the background only can be styled).
>> Yet, I do not ask someone else to fix this, but hope to come up with some
>> support for that in the code base of the widgets by myself.
>>
>> But it would be nice when new widgets came along with the required CSS
>> properties for E4 theming quite from the beginning.
>> If help is welcome here, I'd be willing to lend a hand (however,
>> unfortunately I cannot  promise constant and quick response).
>>
>> Best,
>>   MP
>>
>> Am Mo., 17. Feb. 2020 um 16:30 Uhr schrieb Laurent Caron <
>> laurent.ca...@gmail.com>:
>>
>>> Hi Matthias,
>>>
>>> Thank you for your message. I wrote many new widgets and I have to admit
>>> that I did not take care of this aspect (probably because I'm not able to
>>> work with the Dark Theme of Eclipse or VSCode).
>>>
>>> When you are talking about theming, you're talking about e4 theming,
>>> right ? (like the dark mode in Eclipse)
>>>
>>> Can you tell what widgets cause problem in your application ? Or post a
>>> screenshot if possible ?
>>>
>>> Thank you for your feedback,
>>>
>>> Laurent
>>>
>>>
>>> Le lun. 17 févr. 2020 à 13:50, Matthias Paul Scholz <
>>> matthias.paul.sch...@gmail.com> a écrit :
>>>
>>>> Hi all,
>>>>
>>>> I see a lot of new widgets being added to our beloved Nebula lately
>>>> which is great!
>>>> Yet, I wonder whether also support for theming is considered by the
>>>> authors when creating the first release versions for them?
>>>>
>>>> Using a lot of the "classic" Nebula widgets in our RCP application
>>>> (that includes theming as a matter of course), we noticed that theming
>>>> support is rather sparse for the Nebula widgets so far; in my opinion, this
>>>> is some sort of drawback for the acceptance of the Nebula widgets these
>>>> days since good theming support is naturally expected by users of modern
>>>> RCP applications.
>>>>
>>>> Hence, I think it would be reasonable and productive to take theming
>>>> support for new Nebula into account quite from the start.
>>>>
>>>> Best,
>>>>   MP
>>>> ___
>>>> nebula-dev mailing list
>>>> nebula-dev@eclipse.org
>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>> from this list, visit
>>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>>
>>> ___
>>> nebula-dev mailing list
>>> nebula-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Theming support in new widgets?

[Matthias Paul Scholz]

Hi Laurent,

Merci for the quick response.
Indeed, it's E4 theming I was referring too.

Nebula widgets we were not able to style satisfyingly were in particular
the TableCombo and the CDateTime widget (for the TableCombo the text field
border and the button do not seem to be accessible for theming, while with
the  CDateTimeWidget more or less the background only can be styled).
Yet, I do not ask someone else to fix this, but hope to come up with some
support for that in the code base of the widgets by myself.

But it would be nice when new widgets came along with the required CSS
properties for E4 theming quite from the beginning.
If help is welcome here, I'd be willing to lend a hand (however,
unfortunately I cannot  promise constant and quick response).

Best,
  MP

Am Mo., 17. Feb. 2020 um 16:30 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Hi Matthias,
>
> Thank you for your message. I wrote many new widgets and I have to admit
> that I did not take care of this aspect (probably because I'm not able to
> work with the Dark Theme of Eclipse or VSCode).
>
> When you are talking about theming, you're talking about e4 theming, right
> ? (like the dark mode in Eclipse)
>
> Can you tell what widgets cause problem in your application ? Or post a
> screenshot if possible ?
>
> Thank you for your feedback,
>
> Laurent
>
>
> Le lun. 17 févr. 2020 à 13:50, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> a écrit :
>
>> Hi all,
>>
>> I see a lot of new widgets being added to our beloved Nebula lately which
>> is great!
>> Yet, I wonder whether also support for theming is considered by the
>> authors when creating the first release versions for them?
>>
>> Using a lot of the "classic" Nebula widgets in our RCP application (that
>> includes theming as a matter of course), we noticed that theming support is
>> rather sparse for the Nebula widgets so far; in my opinion, this is some
>> sort of drawback for the acceptance of the Nebula widgets these days since
>> good theming support is naturally expected by users of modern RCP
>> applications.
>>
>> Hence, I think it would be reasonable and productive to take theming
>> support for new Nebula into account quite from the start.
>>
>> Best,
>>   MP
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/nebula-dev

[nebula-dev] Theming support in new widgets?

[Matthias Paul Scholz]

Hi all,

I see a lot of new widgets being added to our beloved Nebula lately which
is great!
Yet, I wonder whether also support for theming is considered by the authors
when creating the first release versions for them?

Using a lot of the "classic" Nebula widgets in our RCP application (that
includes theming as a matter of course), we noticed that theming support is
rather sparse for the Nebula widgets so far; in my opinion, this is some
sort of drawback for the acceptance of the Nebula widgets these days since
good theming support is naturally expected by users of modern RCP
applications.

Hence, I think it would be reasonable and productive to take theming
support for new Nebula into account quite from the start.

Best,
  MP
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] New Widget for Nebula

[Matthias Paul Scholz]

Great! :)

Besides, does it support Theming by css-properties?


Am Mo., 18. Feb. 2019 um 17:31 Uhr schrieb Laurent Caron <
laurent.ca...@gmail.com>:

> Good afternoon
>
> I'd like to inform you that I've pushed a new widget to Nebula : *Password
> Revealer* [1]
>
> This widget is an extension of a password text field. It behaves like a
> password widget, but a button is dispayed juste besides the field :
>
> [image: image.png]
>
> When the user clicks on the "eye" button, the password is revealed until
> the user stops clicking.
>
> [image: image.png]
>
> Please have a look at the pull request [2]
>
> Once it's gonna be merge, I'll updte the documentation and the web site.
>
> Regards,
>
> Laurent
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=543398
> [2] https://github.com/eclipse/nebula/pull/45
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] CSS styling of CDateTime?

[Matthias Paul Scholz]

Hi Wim,

Back in 2019.
Find attached a screenshot of a CDateTime drop down instance with VCanvas
styled with a light backgrund color.
The white (day picker) part and the black labels cannot by styled with CSS
presently.

Best,
  MP

Am Fr., 21. Dez. 2018 um 11:07 Uhr schrieb Wim Jongman <
wim.jong...@remainsoftware.com>:

> Right. There are some widgets that use CWT as base.
>
>
>
> Looking at the code I see that VControl constructor determines the initial
> foreground.
>
>
>
> If background is not set explicitly it gets it from vpanel  and vpanel
> parents otherwise from its composite.
>
>
>
> Can you post a screenshot? CDateTime has many faces.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:
> nebula-dev-boun...@eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Friday, 21 December 2018 10:53
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CSS styling of CDateTime?
>
>
>
> Hi Wim,
>
>
>
> Not sure about the reason.
>
> The whole seems to boil down to some
> org.eclipse.nebula.cwt.v.VControlPainter used to paint
> org.eclipse.nebula.cwt.v.VLabel instances; that's a part of the code base I
> am not familiar with, though.
>
> Configuring colors for VLabel in the css file does have no effect.
>
>
>
> Best,
>
>   MP
>
>
>
> Am Fr., 21. Dez. 2018 um 10:42 Uhr schrieb Wim Jongman <
> wim.jong...@remainsoftware.com>:
>
> Hi Matthias,
>
>
>
> Why is the label not styleable?
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:
> nebula-dev-boun...@eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Friday, 21 December 2018 10:03
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CSS styling of CDateTime?
>
>
>
> Hi Wim,
>
>
>
> Thanks for the answer.
>
>
>
> After using CSS spy and looking into the code, I was able to style at
> least the backgound of the parts of CDateTime where the labels appear by
> configuring
>
>
>
> VCanvas {
>
> background-color: ;
>
> }
>
>
>
> That way, I could choose some light background color that makes the
> (presently unmodifiable) foreground color of the labels involved readable
> again; however, that is just an unsatisfying workaround for now.
>
>
>
> However, I think for user acceptance it is mandatory to make CDateTime and
> all the other Nebula widgets satisfyingly themable in the long run.
>
>
>
> Best,
>
>   MP
>
>
>
>
>
>
>
>
>
>
>
> Am Mi., 19. Dez. 2018 um 18:50 Uhr schrieb Wim Jongman <
> wim.jong...@remainsoftware.com>:
>
> Hi Matthias,
>
>
>
> CDateTime is not CSS aware. I know of one widget that is which is the
> pshelf widget. You might want to take a look at that.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:
> nebula-dev-boun...@eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Wednesday, 19 December 2018 15:50
> *To:* Nebula Dev
> *Subject:* [nebula-dev] CSS styling of CDateTime?
>
>
>
> Hi,
>
>
>
> I am presently in the process of (Dark) theming our RCP application with
> CSS properties.
>
> The application also uses the CDateTime widget from Nebula.
>
>
>
> Works well for the other widgets in our application and for the background
> of the CDateTime widget; however,  the color of the  Labels in the
> different areas of the CDateTime widget stays gray and the background of
> the day picker stays white regardless  what properties I do set in the
> application's .css file.
>
>
>
> Is CDateTime meant to be stylable by CSS properties?
>
> Do I need to register a particular IElementProvider or property handler?
>
> Does anyone have an example which properties need to be set?
>
>
>
> Thanks and best,
>
>   MP
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] CSS styling of CDateTime?

[Matthias Paul Scholz]

Hi Wim,

Not sure about the reason.
The whole seems to boil down to some
org.eclipse.nebula.cwt.v.VControlPainter used to paint
org.eclipse.nebula.cwt.v.VLabel instances; that's a part of the code base I
am not familiar with, though.
Configuring colors for VLabel in the css file does have no effect.

Best,
  MP

Am Fr., 21. Dez. 2018 um 10:42 Uhr schrieb Wim Jongman <
wim.jong...@remainsoftware.com>:

> Hi Matthias,
>
>
>
> Why is the label not styleable?
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:
> nebula-dev-boun...@eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Friday, 21 December 2018 10:03
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CSS styling of CDateTime?
>
>
>
> Hi Wim,
>
>
>
> Thanks for the answer.
>
>
>
> After using CSS spy and looking into the code, I was able to style at
> least the backgound of the parts of CDateTime where the labels appear by
> configuring
>
>
>
> VCanvas {
>
> background-color: ;
>
> }
>
>
>
> That way, I could choose some light background color that makes the
> (presently unmodifiable) foreground color of the labels involved readable
> again; however, that is just an unsatisfying workaround for now.
>
>
>
> However, I think for user acceptance it is mandatory to make CDateTime and
> all the other Nebula widgets satisfyingly themable in the long run.
>
>
>
> Best,
>
>   MP
>
>
>
>
>
>
>
>
>
>
>
> Am Mi., 19. Dez. 2018 um 18:50 Uhr schrieb Wim Jongman <
> wim.jong...@remainsoftware.com>:
>
> Hi Matthias,
>
>
>
> CDateTime is not CSS aware. I know of one widget that is which is the
> pshelf widget. You might want to take a look at that.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:
> nebula-dev-boun...@eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Wednesday, 19 December 2018 15:50
> *To:* Nebula Dev
> *Subject:* [nebula-dev] CSS styling of CDateTime?
>
>
>
> Hi,
>
>
>
> I am presently in the process of (Dark) theming our RCP application with
> CSS properties.
>
> The application also uses the CDateTime widget from Nebula.
>
>
>
> Works well for the other widgets in our application and for the background
> of the CDateTime widget; however,  the color of the  Labels in the
> different areas of the CDateTime widget stays gray and the background of
> the day picker stays white regardless  what properties I do set in the
> application's .css file.
>
>
>
> Is CDateTime meant to be stylable by CSS properties?
>
> Do I need to register a particular IElementProvider or property handler?
>
> Does anyone have an example which properties need to be set?
>
>
>
> Thanks and best,
>
>   MP
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] CSS styling of CDateTime?

[Matthias Paul Scholz]

Hi Wim,

Thanks for the answer.

After using CSS spy and looking into the code, I was able to style at least
the backgound of the parts of CDateTime where the labels appear by
configuring

VCanvas {
background-color: ;
}

That way, I could choose some light background color that makes the
(presently unmodifiable) foreground color of the labels involved readable
again; however, that is just an unsatisfying workaround for now.

However, I think for user acceptance it is mandatory to make CDateTime and
all the other Nebula widgets satisfyingly themable in the long run.

Best,
  MP





Am Mi., 19. Dez. 2018 um 18:50 Uhr schrieb Wim Jongman <
wim.jong...@remainsoftware.com>:

> Hi Matthias,
>
>
>
> CDateTime is not CSS aware. I know of one widget that is which is the
> pshelf widget. You might want to take a look at that.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:
> nebula-dev-boun...@eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Wednesday, 19 December 2018 15:50
> *To:* Nebula Dev
> *Subject:* [nebula-dev] CSS styling of CDateTime?
>
>
>
> Hi,
>
>
>
> I am presently in the process of (Dark) theming our RCP application with
> CSS properties.
>
> The application also uses the CDateTime widget from Nebula.
>
>
>
> Works well for the other widgets in our application and for the background
> of the CDateTime widget; however,  the color of the  Labels in the
> different areas of the CDateTime widget stays gray and the background of
> the day picker stays white regardless  what properties I do set in the
> application's .css file.
>
>
>
> Is CDateTime meant to be stylable by CSS properties?
>
> Do I need to register a particular IElementProvider or property handler?
>
> Does anyone have an example which properties need to be set?
>
>
>
> Thanks and best,
>
>   MP
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/nebula-dev
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/nebula-dev

[nebula-dev] CSS styling of CDateTime?

[Matthias Paul Scholz]

Hi,

I am presently in the process of (Dark) theming our RCP application with
CSS properties.
The application also uses the CDateTime widget from Nebula.

Works well for the other widgets in our application and for the background
of the CDateTime widget; however,  the color of the  Labels in the
different areas of the CDateTime widget stays gray and the background of
the day picker stays white regardless  what properties I do set in the
application's .css file.

Is CDateTime meant to be stylable by CSS properties?
Do I need to register a particular IElementProvider or property handler?
Does anyone have an example which properties need to be set?

Thanks and best,
  MP
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Referendum to Move to Github

[Matthias Paul Scholz]

Can't one just disable issues for the GitHub repository at hand?
https://help.github.com/articles/disabling-issues/

Am Fr., 13. Juli 2018 um 14:03 Uhr schrieb Mickael Istria <
mist...@redhat.com>:

> One important thing in this migration is that since it's not possible
> AFAIK to disable issue reports on GitHub, migrating to GitHub also implies
> more or less moving away from Bugzilla (and even if current contributors
> keep using Bugzilla instead of GitHub issues, it's a matter of time for the
> majority to be on GitHub issues too).
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Referendum to Move to Github

[Matthias Paul Scholz]

+1, yes, yea!

After all that Gerrit horror:
Give me Github or Give me Death!

Am Fr., 13. Juli 2018 um 10:32 Uhr schrieb Wim Jongman <
wim.jong...@gmail.com>:

> Hello All,
>
> I am starting a vote to move to Github [1] or remain with Gerrit.
>
> *Who can vote*
> If you have ever contributed code to Nebula or if you are thinking about
> one day contributing code then you can vote.
>
> *Voting process*
> You can vote +1, Yes or Yea! if you want to *LEAVE Gerrit and move to
> GitHub*
> You can vote -1, No or Nay! if you want to *REMAIN with Gerrit*
>
> In one week we will count the ballots and the results are binding.
>
>
> Best regards,
>
> Wim
>
> [1] https://www.eclipse.org/projects/handbook/#resources-github
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] CDateTime widget: no possibility to specify Realm in CDateTimeObservableValue

[Matthias Paul Scholz]

Hi Wim,

I've contacted you with my new Skype account.

Best,
  MP

2018-05-17 9:40 GMT+02:00 Wim Jongman :

> Hi Matthias,
>
>
>
> I changed the wiki (;
>
>
>
> Please ping me on skype wim.jongman so that we can sort this out.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Thursday, 17 May 2018 08:56
>
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Hi Wim,
>
> Both URLs (with my Geritt user name and, in case of the https channel my
> newly configured passwort) give me
>
> "You are not allowed to perform this operation.
> To push into this reference you need 'Push' rights."
>
> Besides, the https URL you stated differs from the one that is stated on
> the Gerrit nebula page - there it is https://@git.eclipse.org/r/*p*
> /nebula/org.eclipse.nebula (which worked for me some weeks ago still, but
> not any more now).
>
>
>
> 2018-05-16 20:35 GMT+02:00 Wim Jongman :
>
> https url seems to be: https://@git.eclipse.org/r/*a*
> /nebula/org.eclipse.nebula
>
>
>
> https://git.eclipse.org/r/#/admin/projects/nebula/org.eclipse.nebula
>
>
>
> On Wed, May 16, 2018 at 7:14 PM, Wim Jongman  com> wrote:
>
> ssh://@git.eclipse.org:29418/nebula/org.eclipse.nebula.git
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Wednesday, 16 May 2018 16:49
>
>
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Maybe I have used the wrong ssh URL?
>
> Which one do you use?
>
>
>
> 2018-05-16 16:47 GMT+02:00 Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com>:
>
> Actually, I did try both:
>
> 1. Changing password as you proposed.
> 2. Using an ssh key  with an URL starting with ssh (as described in the
> according Gerrit web page).
>
> Same effect for both.
>
>
>
> 2018-05-16 16:32 GMT+02:00 Wim Jongman :
>
> What did you try? Resetting the Gerrit password or doing SSH? In case of
> SSH then the url should also start with ssh.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Wednesday, 16 May 2018 15:05
>
>
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Hi Wim,
>
> Tried that.
>
> Now when pushing to
> https://@git.eclipse.org/r/p/
> nebula/org.eclipse.nebula.git
> I get the message
>
> "prohibited by Gerrit: ref update access denied
> Branch refs/heads/master:
> You are not allowed to perform this operation.
> To push into this reference you need 'Push' rights."
>
> Have I lost my push rights somehow?
>
> Best,
>
>   MP
>
>
>
> 2018-05-11 11:15 GMT+02:00 Wim Jongman :
>
> Hi Matthias,
>
>
>
> I am also puzzled by the Gerrit password and why we need it. I know that
> there has been a change so that it does not show your Gerrit password
> anymore [1]. So the password in Gerrit can only be viewed once. Then you
> have to store it somewhere or regenerate.
>
>
>
> So the next try would be to login with your email in Gerrit and then
> change your Gerrit password in your account and reuse that one.
>
>
>
> I have switched to ssh mode in Gerrit to not use the password anymore. I
> suggest you do the same.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=531018
>
>
>
>
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Friday, 11 May 2018 09:15
>
>
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Hi Wim,
>
> Yet, my Eclipse password does work for login into my Gerrit account only
> for my email adress as user name, but not for the user name configured in
> my Gerrit settings. That one is also used as the username part in the push
> URL in the Gerrit configuration on my local Nebula repository - hence,
> still no success with pushing when using the Eclipse password.
>
> Following the guide in https://wiki.eclipse.org/Nebula/Contribut

Re: [nebula-dev] CDateTime widget: no possibility to specify Realm in CDateTimeObservableValue

[Matthias Paul Scholz]

Hi Wim,

Both URLs (with my Geritt user name and, in case of the https channel my
newly configured passwort) give me

"You are not allowed to perform this operation.
To push into this reference you need 'Push' rights."

Besides, the https URL you stated differs from the one that is stated on
the Gerrit nebula page - there it is https://@git.eclipse.org/r/*p*
/nebula/org.eclipse.nebula (which worked for me some weeks ago still, but
not any more now).

2018-05-16 20:35 GMT+02:00 Wim Jongman <wim.jong...@gmail.com>:

> https url seems to be: https://@git.eclipse.org/r/*a*
> /nebula/org.eclipse.nebula
>
> https://git.eclipse.org/r/#/admin/projects/nebula/org.eclipse.nebula
>
> On Wed, May 16, 2018 at 7:14 PM, Wim Jongman <wim.jongman@remainsoftware.
> com> wrote:
>
>> ssh://@git.eclipse.org:29418/nebula/org.eclipse.nebula.git
>>
>>
>>
>> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@ecl
>> ipse.org] *On Behalf Of *Matthias Paul Scholz
>> *Sent:* Wednesday, 16 May 2018 16:49
>>
>> *To:* Nebula Dev
>> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
>> Realm in CDateTimeObservableValue
>>
>>
>>
>> Maybe I have used the wrong ssh URL?
>>
>> Which one do you use?
>>
>>
>>
>> 2018-05-16 16:47 GMT+02:00 Matthias Paul Scholz <
>> matthias.paul.sch...@gmail.com>:
>>
>> Actually, I did try both:
>>
>> 1. Changing password as you proposed.
>> 2. Using an ssh key  with an URL starting with ssh (as described in the
>> according Gerrit web page).
>>
>> Same effect for both.
>>
>>
>>
>> 2018-05-16 16:32 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:
>>
>> What did you try? Resetting the Gerrit password or doing SSH? In case of
>> SSH then the url should also start with ssh.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Wim
>>
>>
>>
>>
>>
>> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@ecl
>> ipse.org] *On Behalf Of *Matthias Paul Scholz
>> *Sent:* Wednesday, 16 May 2018 15:05
>>
>>
>> *To:* Nebula Dev
>> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
>> Realm in CDateTimeObservableValue
>>
>>
>>
>> Hi Wim,
>>
>> Tried that.
>>
>> Now when pushing to
>> https://@git.eclipse.org/r/p/nebu
>> la/org.eclipse.nebula.git
>> I get the message
>>
>> "prohibited by Gerrit: ref update access denied
>> Branch refs/heads/master:
>> You are not allowed to perform this operation.
>> To push into this reference you need 'Push' rights."
>>
>> Have I lost my push rights somehow?
>>
>> Best,
>>
>>   MP
>>
>>
>>
>> 2018-05-11 11:15 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:
>>
>> Hi Matthias,
>>
>>
>>
>> I am also puzzled by the Gerrit password and why we need it. I know that
>> there has been a change so that it does not show your Gerrit password
>> anymore [1]. So the password in Gerrit can only be viewed once. Then you
>> have to store it somewhere or regenerate.
>>
>>
>>
>> So the next try would be to login with your email in Gerrit and then
>> change your Gerrit password in your account and reuse that one.
>>
>>
>>
>> I have switched to ssh mode in Gerrit to not use the password anymore. I
>> suggest you do the same.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Wim
>>
>>
>>
>> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=531018
>>
>>
>>
>>
>>
>>
>>
>> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@ecl
>> ipse.org] *On Behalf Of *Matthias Paul Scholz
>> *Sent:* Friday, 11 May 2018 09:15
>>
>>
>> *To:* Nebula Dev
>> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
>> Realm in CDateTimeObservableValue
>>
>>
>>
>> Hi Wim,
>>
>> Yet, my Eclipse password does work for login into my Gerrit account only
>> for my email adress as user name, but not for the user name configured in
>> my Gerrit settings. That one is also used as the username part in the push
>> URL in the Gerrit configuration on my local Nebula repository - hence,
>> still no success with pushing when using the Eclipse password.
>>
>> Following the guide in https://wiki.eclipse.org/Nebula/Contributions,
>> one needs to use that username -

Re: [nebula-dev] CDateTime widget: no possibility to specify Realm in CDateTimeObservableValue

[Matthias Paul Scholz]

Maybe I have used the wrong ssh URL?
Which one do you use?

2018-05-16 16:47 GMT+02:00 Matthias Paul Scholz <
matthias.paul.sch...@gmail.com>:

> Actually, I did try both:
> 1. Changing password as you proposed.
> 2. Using an ssh key  with an URL starting with ssh (as described in the
> according Gerrit web page).
>
> Same effect for both.
>
> 2018-05-16 16:32 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:
>
>> What did you try? Resetting the Gerrit password or doing SSH? In case of
>> SSH then the url should also start with ssh.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Wim
>>
>>
>>
>>
>>
>> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@ecl
>> ipse.org] *On Behalf Of *Matthias Paul Scholz
>> *Sent:* Wednesday, 16 May 2018 15:05
>>
>> *To:* Nebula Dev
>> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
>> Realm in CDateTimeObservableValue
>>
>>
>>
>> Hi Wim,
>>
>> Tried that.
>>
>> Now when pushing to
>> https://@git.eclipse.org/r/p/nebu
>> la/org.eclipse.nebula.git
>> I get the message
>>
>> "prohibited by Gerrit: ref update access denied
>> Branch refs/heads/master:
>> You are not allowed to perform this operation.
>> To push into this reference you need 'Push' rights."
>>
>> Have I lost my push rights somehow?
>>
>> Best,
>>
>>   MP
>>
>>
>>
>> 2018-05-11 11:15 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:
>>
>> Hi Matthias,
>>
>>
>>
>> I am also puzzled by the Gerrit password and why we need it. I know that
>> there has been a change so that it does not show your Gerrit password
>> anymore [1]. So the password in Gerrit can only be viewed once. Then you
>> have to store it somewhere or regenerate.
>>
>>
>>
>> So the next try would be to login with your email in Gerrit and then
>> change your Gerrit password in your account and reuse that one.
>>
>>
>>
>> I have switched to ssh mode in Gerrit to not use the password anymore. I
>> suggest you do the same.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Wim
>>
>>
>>
>> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=531018
>>
>>
>>
>>
>>
>>
>>
>> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@ecl
>> ipse.org] *On Behalf Of *Matthias Paul Scholz
>> *Sent:* Friday, 11 May 2018 09:15
>>
>>
>> *To:* Nebula Dev
>> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
>> Realm in CDateTimeObservableValue
>>
>>
>>
>> Hi Wim,
>>
>> Yet, my Eclipse password does work for login into my Gerrit account only
>> for my email adress as user name, but not for the user name configured in
>> my Gerrit settings. That one is also used as the username part in the push
>> URL in the Gerrit configuration on my local Nebula repository - hence,
>> still no success with pushing when using the Eclipse password.
>>
>> Following the guide in https://wiki.eclipse.org/Nebula/Contributions,
>> one needs to use that username - and I remember that it worked well in the
>> past.
>>
>> Puzzled,
>>
>>   MP
>>
>>
>>
>> 2018-05-10 20:16 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:
>>
>> Hi Matthias,
>>
>>
>>
>> For that you just use your normal Eclipse password.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Wim
>>
>>
>>
>> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@ecl
>> ipse.org] *On Behalf Of *Matthias Paul Scholz
>> *Sent:* Thursday, 10 May 2018 17:05
>> *To:* Nebula Dev
>> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
>> Realm in CDateTimeObservableValue
>>
>>
>>
>> Hi Wim,
>>
>> I tried to push a patch today, but for some reason, my Gerrit password
>> (which worked fine some weeks ago) is not accepted any more.
>> It doesn't work when trying to log in on the web site (
>> https://git.eclipse.org/r/login) neither.
>>
>> Best,
>>
>>   MP
>>
>>
>>
>> 2018-04-16 10:37 GMT+02:00 Wim Jongman <wim.jong...@gmail.com>:
>>
>> Hi Matthias,
>>
>> Please file an issue and a patch, I will merge it.
>>
>> Cheers,
>>
>> Wim
>>
>>
>>

Re: [nebula-dev] CDateTime widget: no possibility to specify Realm in CDateTimeObservableValue

[Matthias Paul Scholz]

Actually, I did try both:
1. Changing password as you proposed.
2. Using an ssh key  with an URL starting with ssh (as described in the
according Gerrit web page).

Same effect for both.

2018-05-16 16:32 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:

> What did you try? Resetting the Gerrit password or doing SSH? In case of
> SSH then the url should also start with ssh.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Wednesday, 16 May 2018 15:05
>
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Hi Wim,
>
> Tried that.
>
> Now when pushing to
> https://@git.eclipse.org/r/p/
> nebula/org.eclipse.nebula.git
> I get the message
>
> "prohibited by Gerrit: ref update access denied
> Branch refs/heads/master:
> You are not allowed to perform this operation.
> To push into this reference you need 'Push' rights."
>
> Have I lost my push rights somehow?
>
> Best,
>
>   MP
>
>
>
> 2018-05-11 11:15 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:
>
> Hi Matthias,
>
>
>
> I am also puzzled by the Gerrit password and why we need it. I know that
> there has been a change so that it does not show your Gerrit password
> anymore [1]. So the password in Gerrit can only be viewed once. Then you
> have to store it somewhere or regenerate.
>
>
>
> So the next try would be to login with your email in Gerrit and then
> change your Gerrit password in your account and reuse that one.
>
>
>
> I have switched to ssh mode in Gerrit to not use the password anymore. I
> suggest you do the same.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=531018
>
>
>
>
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Friday, 11 May 2018 09:15
>
>
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Hi Wim,
>
> Yet, my Eclipse password does work for login into my Gerrit account only
> for my email adress as user name, but not for the user name configured in
> my Gerrit settings. That one is also used as the username part in the push
> URL in the Gerrit configuration on my local Nebula repository - hence,
> still no success with pushing when using the Eclipse password.
>
> Following the guide in https://wiki.eclipse.org/Nebula/Contributions, one
> needs to use that username - and I remember that it worked well in the past.
>
> Puzzled,
>
>   MP
>
>
>
> 2018-05-10 20:16 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:
>
> Hi Matthias,
>
>
>
> For that you just use your normal Eclipse password.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Thursday, 10 May 2018 17:05
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Hi Wim,
>
> I tried to push a patch today, but for some reason, my Gerrit password
> (which worked fine some weeks ago) is not accepted any more.
> It doesn't work when trying to log in on the web site (
> https://git.eclipse.org/r/login) neither.
>
> Best,
>
>   MP
>
>
>
> 2018-04-16 10:37 GMT+02:00 Wim Jongman <wim.jong...@gmail.com>:
>
> Hi Matthias,
>
> Please file an issue and a patch, I will merge it.
>
> Cheers,
>
> Wim
>
>
>
> On Thu, Apr 12, 2018 at 10:13 AM, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
> Hi,
>
> I'm presently trying to integrate the CDateTime widget into our RCP
> application. Since it heavily relies on databinding, I was happy to find a
> CDateTimeObservableValue in Nebula that allows for binding external models
> to the CDateTime widget. :)
>
> However, when writing a SWTBot test for the widget, I have noticed that it
> falis due to the fact that the CDateTimeObservableValue internally uses
> Realm.getDefault() which gives rise to an exception in the the base
> AbstractObservableValue in case of unit tests.
>
> What is missing here is an additional constructor for
> CDateTimeObservableValue that also takes a Realm instance and delegat

Re: [nebula-dev] CDateTime widget: no possibility to specify Realm in CDateTimeObservableValue

[Matthias Paul Scholz]

Hi Wim,

Tried that.
Now when pushing to
https://@
git.eclipse.org/r/p/nebula/org.eclipse.nebula.git
I get the message

"prohibited by Gerrit: ref update access denied
Branch refs/heads/master:
You are not allowed to perform this operation.
To push into this reference you need 'Push' rights."

Have I lost my push rights somehow?

Best,
  MP

2018-05-11 11:15 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:

> Hi Matthias,
>
>
>
> I am also puzzled by the Gerrit password and why we need it. I know that
> there has been a change so that it does not show your Gerrit password
> anymore [1]. So the password in Gerrit can only be viewed once. Then you
> have to store it somewhere or regenerate.
>
>
>
> So the next try would be to login with your email in Gerrit and then
> change your Gerrit password in your account and reuse that one.
>
>
>
> I have switched to ssh mode in Gerrit to not use the password anymore. I
> suggest you do the same.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=531018
>
>
>
>
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Friday, 11 May 2018 09:15
>
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Hi Wim,
>
> Yet, my Eclipse password does work for login into my Gerrit account only
> for my email adress as user name, but not for the user name configured in
> my Gerrit settings. That one is also used as the username part in the push
> URL in the Gerrit configuration on my local Nebula repository - hence,
> still no success with pushing when using the Eclipse password.
>
> Following the guide in https://wiki.eclipse.org/Nebula/Contributions, one
> needs to use that username - and I remember that it worked well in the past.
>
> Puzzled,
>
>   MP
>
>
>
> 2018-05-10 20:16 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:
>
> Hi Matthias,
>
>
>
> For that you just use your normal Eclipse password.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Thursday, 10 May 2018 17:05
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Hi Wim,
>
> I tried to push a patch today, but for some reason, my Gerrit password
> (which worked fine some weeks ago) is not accepted any more.
> It doesn't work when trying to log in on the web site (
> https://git.eclipse.org/r/login) neither.
>
> Best,
>
>   MP
>
>
>
> 2018-04-16 10:37 GMT+02:00 Wim Jongman <wim.jong...@gmail.com>:
>
> Hi Matthias,
>
> Please file an issue and a patch, I will merge it.
>
> Cheers,
>
> Wim
>
>
>
> On Thu, Apr 12, 2018 at 10:13 AM, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
> Hi,
>
> I'm presently trying to integrate the CDateTime widget into our RCP
> application. Since it heavily relies on databinding, I was happy to find a
> CDateTimeObservableValue in Nebula that allows for binding external models
> to the CDateTime widget. :)
>
> However, when writing a SWTBot test for the widget, I have noticed that it
> falis due to the fact that the CDateTimeObservableValue internally uses
> Realm.getDefault() which gives rise to an exception in the the base
> AbstractObservableValue in case of unit tests.
>
> What is missing here is an additional constructor for
> CDateTimeObservableValue that also takes a Realm instance and delegates to
> the according constructor in AbstractObservableValue.
>
> /MP
>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] CDateTime widget: no possibility to specify Realm in CDateTimeObservableValue

[Matthias Paul Scholz]

Hi Wim,

Yet, my Eclipse password does work for login into my Gerrit account only
for my email adress as user name, but not for the user name configured in
my Gerrit settings. That one is also used as the username part in the push
URL in the Gerrit configuration on my local Nebula repository - hence,
still no success with pushing when using the Eclipse password.

Following the guide in https://wiki.eclipse.org/Nebula/Contributions, one
needs to use that username - and I remember that it worked well in the past.

Puzzled,
  MP

2018-05-10 20:16 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:

> Hi Matthias,
>
>
>
> For that you just use your normal Eclipse password.
>
>
>
> Cheers,
>
>
>
> Wim
>
>
>
> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@
> eclipse.org] *On Behalf Of *Matthias Paul Scholz
> *Sent:* Thursday, 10 May 2018 17:05
> *To:* Nebula Dev
> *Subject:* Re: [nebula-dev] CDateTime widget: no possibility to specify
> Realm in CDateTimeObservableValue
>
>
>
> Hi Wim,
>
> I tried to push a patch today, but for some reason, my Gerrit password
> (which worked fine some weeks ago) is not accepted any more.
> It doesn't work when trying to log in on the web site (
> https://git.eclipse.org/r/login) neither.
>
> Best,
>
>   MP
>
>
>
> 2018-04-16 10:37 GMT+02:00 Wim Jongman <wim.jong...@gmail.com>:
>
> Hi Matthias,
>
> Please file an issue and a patch, I will merge it.
>
> Cheers,
>
> Wim
>
>
>
> On Thu, Apr 12, 2018 at 10:13 AM, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
> Hi,
>
> I'm presently trying to integrate the CDateTime widget into our RCP
> application. Since it heavily relies on databinding, I was happy to find a
> CDateTimeObservableValue in Nebula that allows for binding external models
> to the CDateTime widget. :)
>
> However, when writing a SWTBot test for the widget, I have noticed that it
> falis due to the fact that the CDateTimeObservableValue internally uses
> Realm.getDefault() which gives rise to an exception in the the base
> AbstractObservableValue in case of unit tests.
>
> What is missing here is an additional constructor for
> CDateTimeObservableValue that also takes a Realm instance and delegates to
> the according constructor in AbstractObservableValue.
>
> /MP
>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] CDateTime widget: no possibility to specify Realm in CDateTimeObservableValue

[Matthias Paul Scholz]

Hi Wim,

I tried to push a patch today, but for some reason, my Gerrit password
(which worked fine some weeks ago) is not accepted any more.
It doesn't work when trying to log in on the web site (
https://git.eclipse.org/r/login) neither.

Best,
  MP

2018-04-16 10:37 GMT+02:00 Wim Jongman <wim.jong...@gmail.com>:

> Hi Matthias,
>
> Please file an issue and a patch, I will merge it.
>
> Cheers,
>
> Wim
>
>
> On Thu, Apr 12, 2018 at 10:13 AM, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
>> Hi,
>>
>> I'm presently trying to integrate the CDateTime widget into our RCP
>> application. Since it heavily relies on databinding, I was happy to find a
>> CDateTimeObservableValue in Nebula that allows for binding external models
>> to the CDateTime widget. :)
>>
>> However, when writing a SWTBot test for the widget, I have noticed that
>> it falis due to the fact that the CDateTimeObservableValue internally uses
>> Realm.getDefault() which gives rise to an exception in the the base
>> AbstractObservableValue in case of unit tests.
>>
>> What is missing here is an additional constructor for
>> CDateTimeObservableValue that also takes a Realm instance and delegates to
>> the according constructor in AbstractObservableValue.
>>
>> /MP
>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] New widgets available on Nebula examples perspective?

[Matthias Paul Scholz]

I like the idea of having a "web style" Nebula examples view and to present
also some code snippets as a quickstart there.

Why not gear to the style of the Eclipse Welcome page, however?
We could use some Nebula widgets itself for that, like the Gallery or the
Launcher.

/MP


2018-04-11 22:35 GMT+02:00 Laurent Caron <laurent.ca...@gmail.com>:

> Hi Wim,
>
> I'm exactly your opposite: I'm not very creative, but I'm not afraid to
> code (sometimes crazy) good ideas.
>
> Example page is indeed not very sexy and is not very useful in fact :(
>
> I think we can make this application looks like a "web page" library
> sample, something like this :
> - You have a menu with the list of all widgets on the left side, with some
> button
> - When you click on a button, you have a composite with a little
> explanation, a widget sample and an excerpt of the code used in the sample.
>
> What do you think of that ?
>
> Good evening
>
> Laurent
>
> 2018-04-11 17:48 GMT+02:00 Wim Jongman <wim.jong...@remainsoftware.com>:
>
>> Hi Matthias,
>>
>>
>>
>> The example page needs a complete overhaul. It is very buggy and not so
>> nice to play with. I some ideas but I am reluctant to share (because
>> usually the man with the idea must also do the programming :):
>>
>>
>>
>> I love to discuss some ideas on this list on how to redo the examples
>> view.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Wim
>>
>>
>>
>>
>>
>>
>>
>> *From:* nebula-dev-boun...@eclipse.org [mailto:nebula-dev-bounces@ecl
>> ipse.org] *On Behalf Of *Matthias Paul Scholz
>> *Sent:* Wednesday, 11 April 2018 13:59
>> *To:* Nebula
>> *Subject:* [nebula-dev] New widgets available on Nebula examples
>> perspective?
>>
>>
>>
>> Hi all,
>>
>> To get an actual look on the widgets that are presently available in the
>> new Nebula 2.0 release (in particular the Opal ones) , I have installed the
>> Nebula example perspective using the update site specified on the Nebula
>> download page (http://download.eclipse.org/nebula/releases/latest).
>>
>> However, I have noticed that only a minor subset of the widgets is
>> included presently there, isn't it?
>>
>> If so, is anyone already working on including all the widgets in the
>> examples perspective?
>>
>> Would be nice to be able to demonstrate all the widgets and their
>> capabilities to someone in an easy manner, in particular the new Opal ones.
>>
>>
>>
>> Best,
>>
>>   MP
>>
>>
>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Final days..

[Matthias Paul Scholz]

Sorry that I didn't find the time to work on the resolution (as originally
intended).

2018-03-15 17:38 GMT+01:00 Wim Jongman <wim.jong...@gmail.com>:

> Thanks, Matthias, I have reopened this.
>
> On Wed, Mar 14, 2018 at 1:26 PM, Matthias Paul Scholz <
> matthias.paul.sch...@gmail.com> wrote:
>
>> I've noticed that Bug #514731 has been set to "Fixed" but I can't see any
>> code that has been checked in for the actual resolution of the bug, only
>> the test that reproduces it?
>>
>> 2018-03-13 12:15 GMT+01:00 Wim Jongman <wim.jong...@gmail.com>:
>>
>>> Dear Committers,
>>>
>>> We are running towards the finals days of the release period. I am going
>>> to ask for a review in a few days.
>>>
>>> Please go over your bugs [1]. They should be fixed, closed or moved to
>>> the next milestone 2.1.0.
>>>
>>> Please add your work to the New and Noteworthy [2].
>>>
>>> Cheers,
>>>
>>> Wim
>>>
>>> [1] https://projects.eclipse.org/projects/technology.nebula/rele
>>> ases/2.0.0/bugs
>>> [2] https://wiki.eclipse.org/Nebula/Releases/2.0.0/NaN
>>>
>>> ___
>>> nebula-dev mailing list
>>> nebula-dev@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>>>
>>
>>
>> ___
>> nebula-dev mailing list
>> nebula-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>>
>
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Final days..

[Matthias Paul Scholz]

I've noticed that Bug #514731 has been set to "Fixed" but I can't see any
code that has been checked in for the actual resolution of the bug, only
the test that reproduces it?

2018-03-13 12:15 GMT+01:00 Wim Jongman :

> Dear Committers,
>
> We are running towards the finals days of the release period. I am going
> to ask for a review in a few days.
>
> Please go over your bugs [1]. They should be fixed, closed or moved to the
> next milestone 2.1.0.
>
> Please add your work to the New and Noteworthy [2].
>
> Cheers,
>
> Wim
>
> [1] https://projects.eclipse.org/projects/technology.nebula/
> releases/2.0.0/bugs
> [2] https://wiki.eclipse.org/Nebula/Releases/2.0.0/NaN
>
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Re: [nebula-dev] Building Nebula

[Matthias Paul Scholz]

Hi Lars,

The issue seems to arise from the fact that the top level container pom
contains the two modules

- releng/org.eclipse.nebula.nebula-release
- releng/org.eclipse.nebula.nebula-incubation

In both of these modules, the module
../../examples/org.eclipse.nebula.examples
is referenced, which appears to violate the constraint that "The
coordinates for a project as given by its group id, artifact id and version
must be unique within a reactor build".

Hence with the actual state of the module structure, I guess you need to
build on the level of one of the two modules stated above instead of on the
Nebula project top level.

Best,
  MP



2018-02-12 11:54 GMT+01:00 Lars Vogel :

> Hi,
>
> how do I build the Nebula project?
>
> mvn clean verify result in the following error:
>
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Project
> 'org.eclipse.nebula:org.eclipse.nebula.examples:1.0.4-SNAPSHOT' is
> duplicated in the reactor @
> [ERROR] Project
> 'org.eclipse.nebula:org.eclipse.nebula.examples:1.0.4-SNAPSHOT' is
> duplicated in the reactor -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DuplicateProjectException
>
> Or is this simply a bug?
>
> Best regards, Lars
>
> --
> Eclipse Platform project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
> http://www.vogella.com
> ___
> nebula-dev mailing list
> nebula-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
___
nebula-dev mailing list
nebula-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

[MediaWiki-l] Alternate mailer program / UserMailer.php

[Matthias Paul]

___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

[MediaWiki-l] Alternate mailer program / UserMailer.php

[Matthias Paul]

Sorry for the empty mail before this, dont know what happened. Mail text  
_now_ attached.

-

Dear MediaWiki community,


I'm trying to install a MediaWiki instance. Although I never worked with  
MediaWiki before, I feel quite comfortable with server issues (*nix) and  
PHP.


I'd like to have mail support in the MW instance. Unfortunately I cannot  
rely on sendmail (or even mini_sendmail) binary in my installation for  
several reasons - both requiring a shell binary.
It seems, it's possible to replace original PHP's mail() command by an  
alternate mailer program.


a) Is includes/UserMailer.php the main and only spot where mail  
functionality code can be spotted?
b) I read about hooks in mailer class code (line 288 of  
https://doc.wikimedia.org/mediawiki-core/master/php/html/UserMailer_8php_source.html):
$ret = wfRunHooks( 'AlternateUserMailer', array( $headers, $to, $from,  
$subject, $body ) );

Is this hook meant to replace the original mail program?
c) Did anyone replace original mailing code by PHPMailer yet?
d) Or is it easier to just use PEAR::Mail instead of PHPMailer (there  
seemed to be some code about PEAR in it)?


Thank you for reading,
Matthias
___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Re: [MediaWiki-l] Alternate mailer program / UserMailer.php

[Matthias Paul]

Am 18.11.2013, 11:38 Uhr, schrieb Daniel Friesen  
dan...@nadir-seen-fire.com:



On 2013-11-18 1:07 AM, Matthias Paul wrote:

I'm trying to install a MediaWiki instance. Although I never worked
with MediaWiki before, I feel quite comfortable with server issues
(*nix) and PHP.

I'd like to have mail support in the MW instance. Unfortunately I
cannot rely on sendmail (or even mini_sendmail) binary in my
installation for several reasons - both requiring a shell binary.
It seems, it's possible to replace original PHP's mail() command by an
alternate mailer program.

Have you tried using $wgSMTP?


No, I didn't. It says: This setting requires PEAR's Mail package to be  
installed [..] and your response seems to direct me to _not_ use  
PEAR-Mail.



a) Is includes/UserMailer.php the main and only spot where mail
functionality code can be spotted?

It should be. A quick ack/grep doesn't show anything else.


Thank you!


b) I read about hooks in mailer class code (line 288 of
https://doc.wikimedia.org/mediawiki-core/master/php/html/UserMailer_8php_source.html):
$ret = wfRunHooks( 'AlternateUserMailer', array( $headers, $to, $from,
$subject, $body ) );
Is this hook meant to replace the original mail program?

Yes that hook allows an extension to override the mail()/PEAR::Mail
handling and implement an alternative mailer backend.

c) Did anyone replace original mailing code by PHPMailer yet?

Not that I know of. But it would be a nice project.
PHPMailer is pretty nice, it's even in composer too.
Which makes me a little happy, while also reminding me that someone has
made a feature our lack of a composer.json file – which we could
otherwise have put a PHPMailer into, incorporated composer into the
release process depending on libraries directly, and not having to go
and shove a big blob of 3rd party code into our codebase with absolutely
no handling for when it becomes outdated.


I'm not sure, if I understood your answer on c. I havent worked with  
Composer or MediaWiki code-wise yet.
Composer is a dependency-management tool, which allows to package  
components (e.g. PhpMailer) as extension? Will the extension be the  
AlternateUsermailer hook, bundled with dependency on PhpMailer?






d) Or is it easier to just use PEAR::Mail instead of PHPMailer (there
seemed to be some code about PEAR in it)?

Nah it's just another part of MW that is legacy code with a bit of NIH
sprinkled on it.


Thank you for reading,
Matthias


~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]



So far, thank you for your answers :)
Matthias

___
MediaWiki-l mailing list
MediaWiki-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Deprecated properties in nutch-default.xml

[Matthias Paul]

Hi,

in nutch-site.xml the description for the property
fetcher.server.min.delay still mentions fetcher.threads.per.host.
Shouldn't this be replaced with fetcher.threads.per.queue?

Are there any plans to remove deprecated properties from nutch-default.xml?
For example generate.max.per.host and db.default.fetch.interval were
already deprecated in Nutch 1.2 (perhaps also before).

Matthias

Re: disable filtering and normalization in the crawl-tool

[Matthias Paul]

Why? Unnecessary pages are already filtered out in the parse step?

On Tue, Jun 12, 2012 at 12:52 AM, remi tassing tassingr...@gmail.com wrote:
 Certainty, but you might need them to avoid crawling unnecessary pages

 On Monday, June 11, 2012, Matthias Paul wrote:

 Hi,

 wouldn't it be better performance-wise to disable filtering and
 normalization in the crawl-tool in the generate, update and invert
 link steps?
 Filtering and normalization shouldn't be needed in these steps, right?

 Matthias

disable filtering and normalization in the crawl-tool

[Matthias Paul]

Hi,

wouldn't it be better performance-wise to disable filtering and
normalization in the crawl-tool in the generate, update and invert
link steps?
Filtering and normalization shouldn't be needed in these steps, right?

Matthias

Re: Linkdb empty

[Matthias Paul]

Both db.ignore.internal.links and db.ignore.external.links are true in my case.
Since I crawl only one domain, I suppose setting
db.ignore.external.links to true is a good idea.

So db.ignore.internal.links should be false?

From what I understand db.ignore.external.links is a setting for the
crawldb, while db.ignore.internal.links is a setting for the linkdb?



On Wed, Jun 6, 2012 at 10:02 AM, Markus Jelsma
markus.jel...@openindex.io wrote:

 -Original message-
 From:Matthias Paul magethle.nu...@gmail.com
 Sent: Wed 06-Jun-2012 09:47
 To: user@nutch.apache.org
 Subject: Linkdb empty

 Hi all,

 hi


 I noticed that my linkdb is always empty although I use the generated
 segments from the last crawl for the generation of the linkdb.

 Check the db.ignore.* settings in your config.

 Do I have to keep more segments?
 As I use Solr for indexing, I only keep the segments from the last crawl.

 You can discard the segments if you never do a full reindex.


 Thanks
 Matthias

Exclude certain mime-types

[Matthias Paul]

How can I exlude certain mime-types from crawling, for example Word-documents?
If I have parse-tika in plugin.includes it will parse them. Do I have
to change parse-plugins.xml?

I can't exclude them in regex-urlfilter as the .doc extension is not
present in the urls.

Thanks
Matthias

Re: [VOTE] Apache Nutch 1.5 release rc #1

[Matthias Paul]

When will Nutch 1.5 be released?

Matthias

On Wed, Apr 18, 2012 at 1:46 PM, Bharat Goyal bharat.go...@shiksha.com wrote:
 +1


 On Monday 16 April 2012 12:34 PM, Markus Jelsma wrote:

  +1

  On Mon, 16 Apr 2012 05:43:22 +, Mattmann, Chris A (388J)
  chris.a.mattm...@jpl.nasa.gov  wrote:

 Hi Folks,

 A candidate for the Nutch 1.5 release is available at:

   http://people.apache.org/~mattmann/apache-nutch-1.5/rc1/

 The release candidate is a zip and tar.gz archive of the sources in:

   http://svn.apache.org/repos/asf/nutch/tags/release-1.5/

 And a binary build suitable for deployment.

 A staged Maven repository is available here:


 https://repository.apache.org/content/repositories/orgapachenutch-054/

 Please vote on releasing this package as Apache Nutch 1.5.
 The vote is open for the next 72 hours and passes if a majority of at
 least three +1 Nutch PMC votes are cast.

   [ ] +1 Release this package as Apache Nutch 1.5
   [ ] -1 Do not release this package because...

 Thanks!

 Cheers,
 Chris

 P.S. Here's my +1.

 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:   http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++



 DISCLAIMER
 This email is intended only for the person or the entity to whom it is
 addressed and may contain information which is confidential and privileged.
 Any review, retransmission, dissemination or any other use of the said
 information by person or entities other than intended recipient is
 unauthorized and prohibited. If you are not the intended recipient, please
 delete this email and contact the sender.

Re: Crawl-tool for iterative crawling?

[Matthias Paul]

In was confused by this tutorial: http://wiki.apache.org/nutch/NutchTutorial
Reading this page one might get to the conclusion that the crawl tool
can't do iterative crawling, because under 3.2 Using Individual
Commands for Whole-Web Crawling there's  the sentence This also
permits ... incremental crawling, as if the crawl command described
before (3.1 Using the Crawl Command) couldn't do that.

Could someone perhaps improve this part of the tutorial?

Matthias






On Thu, May 10, 2012 at 8:39 PM, Markus Jelsma
markus.jel...@openindex.io wrote:

 By default each crawl is iterative. The crawl command is nothing more than a 
 wrapper around the individual crawl cycle commands. The depth parameter is 
 nothing more than executing a single crawl cycle multiple times. This is, if 
 i am not mistaken, also true for older releases, certainly 1.2 and above.


 On Thu, 10 May 2012 19:31:27 +0100, Lewis John Mcgibbney 
 lewis.mcgibb...@gmail.com wrote:

 For the record, there is a patch pending review for Nutchgora which
 will sort part of this for you as well.

 https://issues.apache.org/jira/browse/NUTCH-1301

 Susam Pal also contributed a patch for Nutchgora regarding incremental
 indexing but I can't find it just now sorry.

 Lewis


 On Thu, May 10, 2012 at 5:18 PM, Matthias Paul
 magethle.nu...@gmail.com wrote:

 Hi all,

 can the crawl-command also be used for iterative crawls?
 In older Nutch-versions this was not possible but in 1.5 it seems to work?

 Thanks
 Matthias


 --
 Markus Jelsma - CTO - Openindex

Re: Switched to Tomcat

[Matthias Paul]

Perhaps you are sending a field to Solr which you didn't configure in Solr?
Then the SolrIndexer will break.
Set the loggers to debug and have a look at your log-files.

Matthias

On Sun, Nov 14, 2010 at 7:35 AM, Eric Martin e...@makethembite.com wrote:

 Hello,



 I switched from Jetty to Tomcat. I have a Solr instance running and I can
 go
 to localhost:8080/solr/admin. My job runs until the end and I get:



 2010-11-14 00:33:07,736 WARN  mapred.LocalJobRunner - job_local_0001

 org.apache.solr.common.SolrException: Internal Server Error



 Internal Server Error



 request: http://localhost:8080/solr/update?wt=javabinamp;version=1

at

 org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpS
 olrServer.java:424)

at

 org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpS
 olrServer.java:243)

at

 org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractU
 pdateRequest.java:105)

at
 org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:49)

at
 org.apache.nutch.indexer.solr.SolrWriter.close(SolrWriter.java:75)

at

 org.apache.nutch.indexer.IndexerOutputFormat$1.close(IndexerOutputFormat.jav
 a:48)

at
 org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:474)

at
 org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:411)

at
 org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:216)

 2010-11-14 00:33:07,838 ERROR solr.SolrIndexer - java.io.IOException: Job
 failed!





 Then it breaks. Any ideas?



 Thanks

Re: How to disable document boosting?

[Matthias Paul]

Ok, this works,
thanks.
Matthias

On Sat, Nov 6, 2010 at 10:18 AM, Alexander Aristov 
alexander.aris...@gmail.com wrote:

 disable all scoring plugins then default boost = 1.0 will be applied.

 Best Regards
 Alexander Aristov


 On 5 November 2010 13:05, Matthias Paul magethle.nu...@gmail.com wrote:

  Hi,
 
  how can I disable document boosting?
  I'm indexing to Solr and don't need document boosts (as they boost
  html-pages much more than other content which I have in Solr).
  I found that I have the scoring-opic plugin registered, is this the
  problem?
 
 
  Thanks
  Matthias
 

How to disable document boosting?

[Matthias Paul]

Hi,

how can I disable document boosting?
I'm indexing to Solr and don't need document boosts (as they boost
html-pages much more than other content which I have in Solr).
I found that I have the scoring-opic plugin registered, is this the problem?


Thanks
Matthias

Multilingual html-pages with Nutch and Solr

[Matthias Paul]

Hi,

I'm using Nutch with the language-identifier plugin enabled to detect the
language of the html-pages. For indexing I use a Solr server.
So far everything works but there's one problem: I don't know how to map
multilingual fields to their corresponding Solr-field.
The mapping file solrindex-mapping.xml contains the following:
field dest=lang source=lang/
field dest=title source=title/

But what I would like to have is the following
field dest=lang source=lang/
field dest=title source=title multilingual=true language=lang/
or maybe
field dest=lang source=lang/
field dest=title_${lang} source=title /
so that the title-field gets mapped to title_en for English-pages and
tilte_fr for French pages.

I found the SolrWriter- and SorlMappingReader-classes in the source-code, an
it should be easy to integrate it there.
What do you think? Could this be useful also to others?
Or are there any other solutions out there?

Thanks
Matthias

Re: Multilingual html-pages with Nutch and Solr

[Matthias Paul]

I just created the issue NUTCH-923.
I'll try to provide a patch in the next days.

Matthias

On Wed, Oct 20, 2010 at 4:18 PM, Markus Jelsma
markus.jel...@openindex.iowrote:

 Hi,

 The LanguageIndexingFilter adds a lang field to the NutchDocument object
 which
 in turn can be read in the Solr indexer.

 You other suggestion seems separate from this issue but you could open a
 ticket for that one, or you can use the subcollection plugin to set a
 value,
 although this seems a bit overkill ;)

 Cheers,

 On Wednesday 20 October 2010 16:04:25 Robert Douglass wrote:
  This highlights a general need in this mapping scheme, and yes, the
  ${lang} approach is desirable.
 
  The general need is to be able to pass more information into Solr than
  just a simple 1:1 mapping of existing values to Solr fields. Another
  area where I've run into this need is the case of passing a constant
  field into Solr that identifies this document as coming from Nutch.
 
  In my Solr schema, there is an entity field which tracks the kind of
  document we're dealing with. For those documents coming from Nutch, I'd
  like to be able to do something like:
 
  field dest=entity value=nutch/
  or
  field dest=entity source=some nutch field default=nutch/
  (the second example would only use the default if the source were null)
 
  Note that in the case of ${lang}, this doesn't seem to be one of the
  available NutchField's (see write() in indexer.solr.SolrWriter.java); is
  there a configuration of Nutch that makes language available at that
  point in execution?
 
  On 10/20/2010 03:50 PM, Markus Jelsma wrote:
   Hi,
  
   I believe this is very useful indeed. I'd go for the ${lang} method
   because it allows you to keep your own preferred Solr schema
 namespacing
   for languages. The first method isn't clear on how the fields are named
   in the Solr schema.
  
   Other thoughts in this one?
  
   Could you open an issue in Jira?
  
   Cheers,
  
   On Wednesday, October 20, 2010 09:27:42 am Matthias Paul wrote:
   Hi,
  
   I'm using Nutch with the language-identifier plugin enabled to detect
   the language of the html-pages. For indexing I use a Solr server.
   So far everything works but there's one problem: I don't know how to
 map
   multilingual fields to their corresponding Solr-field.
   The mapping file solrindex-mapping.xml contains the following:
   field dest=lang source=lang/
   field dest=title source=title/
  
   But what I would like to have is the following
   field dest=lang source=lang/
   field dest=title source=title multilingual=true
 language=lang/
   or maybe
   field dest=lang source=lang/
   field dest=title_${lang} source=title /
   so that the title-field gets mapped to title_en for English-pages and
   tilte_fr for French pages.
  
   I found the SolrWriter- and SorlMappingReader-classes in the
   source-code, an it should be easy to integrate it there.
   What do you think? Could this be useful also to others?
   Or are there any other solutions out there?
  
   Thanks
   Matthias

 --
 Markus Jelsma - CTO - Openindex
 http://www.linkedin.com/in/markus17
 050-8536600 / 06-50258350

Exclude html-content from index

[Matthias Paul]

Hi everyone,

I'm using Nutch 1.2 for indexing a intranet-site (with Solr as indexer). I
would like to exclude certain parts of the html-pages like the footer for
example. I found previous posts about this problem but no one with a clear
solution.
Can anyone point me to some relevant documentation? From what I understood I
should write a plugin for an HtmlParseFilter, is that correct?

Thanks
Matthias

Re: [jboss-user] [JNDI and Naming] - EJB 3.1 Global JNDI names

[Matthias Paul Scholz]

Matthias Paul Scholz [http://community.jboss.org/people/mpscholz] replied to 
the discussion

EJB 3.1 Global JNDI names

To view the discussion, visit: http://community.jboss.org/message/542309#542309

--
Looks like this didn't make it into M3 eventually, did it?

--

Reply to this message by going to Community
[http://community.jboss.org/message/542309#542309]

Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2083]

___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Re: [jboss-user] [JNDI and Naming] - EJB 3.1 Global JNDI names

[Matthias Paul Scholz]

Matthias Paul Scholz [http://community.jboss.org/people/mpscholz] replied to 
the discussion

EJB 3.1 Global JNDI names

To view the discussion, visit: http://community.jboss.org/message/542339#542339

--
The 3.1 spec defines portable global JNDI names, by which remote session beans 
are exposed to remote clients, following this syntax:

+java:global[/app-name]/module-name/bean-name[!fully-qualified-interface-name]+

As far as I can see (please correct me if Iam wrong), the JBoss 6 M3 EJB 
container does not expose these names yet, but still the +bean-name/remote+ 
ones only.  :( 

--

Reply to this message by going to Community
[http://community.jboss.org/message/542339#542339]

Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2083]

___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Re: [jboss-user] [JNDI and Naming] - EJB 3.1 Global JNDI names

[Matthias Paul Scholz]

Matthias Paul Scholz [http://community.jboss.org/people/mpscholz] replied to 
the discussion

EJB 3.1 Global JNDI names

To view the discussion, visit: http://community.jboss.org/message/539726#539726

--
As far as I can see, M2 neither doesn't support the EJB 3.1 standard for global 
JNDI names
(java:global[/app-name]/module-name/bean-name), right?

Is there a roadmap yet which milestone of JBoss 6 is going to implement that?

--

Reply to this message by going to Community
[http://community.jboss.org/message/539726#539726]

Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2083]

___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Re: [jboss-user] [JNDI and Naming] - EJB 3.1 Global JNDI names

[Matthias Paul Scholz]

Matthias Paul Scholz [http://community.jboss.org/people/mpscholz] replied to 
the discussion

EJB 3.1 Global JNDI names

To view the discussion, visit: http://community.jboss.org/message/539743#539743

--
Thanks.
That's encouraging to hear.  :) 

--

Reply to this message by going to Community
[http://community.jboss.org/message/539743#539743]

Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1containerType=14container=2083]

___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Re: ScriptRunner question

[Matthias Paul]

Then I'm looking forward to iBatis 3 :)

Doesnt depend on setDelimiter(), it looks as if the newline character is 
trimmed from input script in any case. Patched the file and it works now.

Thank you!
Paule


 Original-Nachricht 
 Datum: Sat, 27 Jun 2009 13:52:38 -0600
 Von: Clinton Begin clinton.be...@gmail.com
 An: user-java@ibatis.apache.org
 Betreff: Re: ScriptRunner question

 No, but in iBATIS 3 there is. :-)
 
 It looks to me that in the example below, you possibly didn't
 setFullLineDelimiter(true);
 
 There's a difference in parsing if the delimiter is the whole line.
 
 Cheers,
 Clinton
 
 On Sat, Jun 27, 2009 at 1:29 PM, Matthias Paul slaye...@gmx.de wrote:
 
  Thank you for your reply, Clinton :)
 
  Is there another supported way to transfer scripts to database yet? Or
 isnt
  iBatis meant to do such tasks?
 
 
  Paule
 
 
   Original-Nachricht 
   Datum: Thu, 25 Jun 2009 18:11:16 -0600
   Von: Clinton Begin clinton.be...@gmail.com
   An: user-java@ibatis.apache.org
   Betreff: Re: ScriptRunner question
 
   ScriptRunner isn't really a supported feature of iBATIS.  It's meant
 for
   utilities and unit tests only.
   Its API may change significantly in the future without warning.
  
   Clinton
  
   On Thu, Jun 25, 2009 at 12:47 PM, slaye...@gmx.de wrote:
  
Hello!
   
Using iBatis 2.3.4.726.
Had some problems with transfering a SQL script (a Oracle package)
 to
Oracle database with iBatis' ScriptRunner.
The SQL script file looked smth like this:
   
   
   
-- MYPACKAGE package specification
create or replace package MYPACKAGE as
   
 -- commentary here
 procedure PROCEDURE1 (
   PARAMETER1 in number
 );
   
 -- insert GVC rule
 procedure PROCEDURE2 (
   PARAMETER1 in number
 );
   
   
end MYPACKAGE;
/
   
   
   
   
   
I called ScriptRunner method setDelimiter(/, true) to set single
   line
delimiter to /. The script was tranfered to database, but on a
 single
   line
with over 20k length, which isnt easy to read or decipher.
   
Mot sure about that, but shouldnt there be a NEWLINE character
 appended
after each line read from the script by
   ScriptRunner.runScript(Connection
conn, Reader reader) ?
   
Another thing is: The if-then-else block starting at line 147 looks
   weird.
I dont understand why some comments are left out (or: written to log
   writer)
while others are not. Are // and -- comment types database
system-dependent?  And isnt the LineNumberReader supposed to return
 the
current line number on errors?
   
   
Thank you for your time!
Paule
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
   
   
 -
To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org
For additional commands, e-mail: user-java-h...@ibatis.apache.org
   
   
 
  --
  GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
  Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
 
  -
  To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org
  For additional commands, e-mail: user-java-h...@ibatis.apache.org
 
 

-- 
Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate
für nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

-
To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org
For additional commands, e-mail: user-java-h...@ibatis.apache.org

Re: ScriptRunner question

[Matthias Paul]

Thank you for your reply, Clinton :)

Is there another supported way to transfer scripts to database yet? Or isnt 
iBatis meant to do such tasks?


Paule


 Original-Nachricht 
 Datum: Thu, 25 Jun 2009 18:11:16 -0600
 Von: Clinton Begin clinton.be...@gmail.com
 An: user-java@ibatis.apache.org
 Betreff: Re: ScriptRunner question

 ScriptRunner isn't really a supported feature of iBATIS.  It's meant for
 utilities and unit tests only.
 Its API may change significantly in the future without warning.
 
 Clinton
 
 On Thu, Jun 25, 2009 at 12:47 PM, slaye...@gmx.de wrote:
 
  Hello!
 
  Using iBatis 2.3.4.726.
  Had some problems with transfering a SQL script (a Oracle package) to
  Oracle database with iBatis' ScriptRunner.
  The SQL script file looked smth like this:
 
 
 
  -- MYPACKAGE package specification
  create or replace package MYPACKAGE as
 
   -- commentary here
   procedure PROCEDURE1 (
 PARAMETER1 in number
   );
 
   -- insert GVC rule
   procedure PROCEDURE2 (
 PARAMETER1 in number
   );
 
 
  end MYPACKAGE;
  /
 
 
 
 
 
  I called ScriptRunner method setDelimiter(/, true) to set single
 line
  delimiter to /. The script was tranfered to database, but on a single
 line
  with over 20k length, which isnt easy to read or decipher.
 
  Mot sure about that, but shouldnt there be a NEWLINE character appended
  after each line read from the script by
 ScriptRunner.runScript(Connection
  conn, Reader reader) ?
 
  Another thing is: The if-then-else block starting at line 147 looks
 weird.
  I dont understand why some comments are left out (or: written to log
 writer)
  while others are not. Are // and -- comment types database
  system-dependent?  And isnt the LineNumberReader supposed to return the
  current line number on errors?
 
 
  Thank you for your time!
  Paule
  --
  GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
  Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
 
  -
  To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org
  For additional commands, e-mail: user-java-h...@ibatis.apache.org
 
 

-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

-
To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org
For additional commands, e-mail: user-java-h...@ibatis.apache.org

[Lejos-discussion] Forum (was: LNP Ports)

[Matthias Paul Scholz]

Jeremy,

Zitat von Jeremy Blair [EMAIL PROTECTED]:

 Secondly, is this the main discussion group for leJOS or has it moved to
 another location? Thanks for any help.

As this mailing list has become another target of spam in the last  
months (which sourceforge obviously is not able or willing to filter  
out), there is a leJOS forum now: http://lejos.sourceforge.net/forum/

Best,
   MP



This message was sent using IMP, the Internet Messaging Program.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

[mojo-user] FIT Maven Plugin does not work for more than one table

[Matthias Paul Scholz]

Hi,

I'm trying to use the FIT Maven plugin.
Everything works fine as long as I have just one table in an HTML
input file (and consequently just one single fixture is triggered).
Yet, when I have more than one table (and thus more than one fixture),
the first fixture is run correctly, but the second one fails - the
stack trace in the output HTML file tells me that the second fixture
fails to get loaded:

java.lang.RuntimeException: The fixture MyTestFixture was not found.
   at fit.Fixture.loadFixture(Unknown Source)
   at fit.Fixture.getLinkedFixtureWithArgs(Unknown Source)
   at fit.Fixture.interpretFollowingTables(Unknown Source)
   at fit.Fixture.interpretTables(Unknown Source)
   at fit.Fixture.doTables(Unknown Source)
   at org.codehaus.mojo.fit.FitRunnerMojo.run(FitRunnerMojo.java:207)
   at org.codehaus.mojo.fit.FitRunnerMojo.run(FitRunnerMojo.java:197)
   at org.codehaus.mojo.fit.FitRunnerMojo.run(FitRunnerMojo.java:190)
   at org.codehaus.mojo.fit.FitRunnerMojo.run(FitRunnerMojo.java:183)
   at org.codehaus.mojo.fit.FitRunnerMojo.execute(FitRunnerMojo.java:116)
   at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)

This happens even when using the same table (and thus the same fixture) twice!

The same input file runs without problems when using FIT from the
command line, so it appears to be an issue of the Maven plugin indeed.

When inspecting the plugin code, one notices that the methods that
trigger the error have been added for FITNESSE. Is the FIT Maven
plugin broken by these changes now?

-- Matthias

-
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Re: [Lejos-discussion] Web Designs for Lejos Web Site

[Matthias Paul Scholz]

Juan,

looks great to me.
Good job!

/Matthias

JAB wrote:
 Hi, I have updated my prototypes for new Lejos Website.
 
 http://www.esmeta.es
 
 user: lejos
 password: nxt
 
 Best Regards.
 
 Juan Antonio Breña Moral
 http://www.juanantonio.info
 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Lejos IDE

[Matthias Paul Scholz]

Hallo Christine,

I've spent some time to enable Markus Heiden's and Jochen Hiller's 
Eclipse 3 leJOS plugin for leJOS 3.0.

Due to spare time constraints, I was only able to take the existing 
sources and update the plug-in's leJOS libraries to leJOS 3.0.0 RC2, but 
not providing any enhancements or fixes to the plug-in itself.

The link to the resulting zip file can be found in the Utilities 
section of www.lejos.org.

Please note that downloading to the RCX brick with the plug-in does 
presently not run on Linux (and I don't know if it ever did(?)).
Hence to this end, on Linux you will have to use the lejos command 
from the command line yet.

Please direct questions regarding the plug-in itself to the plug-in's 
authors (Markus Heiden and Jochen Hiller), using this very list.

Regards,
   Matthias Paul



 
 -Original Message-
 From: Matthias Paul Scholz 
 Sent: Tue 9/5/2006 8:44 AM
 Subject: Re: [Lejos-discussion] Lejos IDE
  
 
My students have used eclipse in the past so I'm sure they would prefer that. 
 
 
 
 Small wonder. Everyone seems to be Eclipsing nowadays (and mostly 
 justifiably so).
 I'll have a look and see what I can do about it - but be prepared not to 
 get it tomorrow already...


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Programming lejos with NXT?

[Matthias Paul Scholz]

Juan,

Juan Antonio Breña Moral [JAB] wrote:

 Then, using Lejos, only i can develop bots with icommand package. currently 
 the best option is NBC, isnt true?

Well, it depends what you want to do in your program(s) and what your 
background is.
There are some NXT programming options available already; see
http://mynxt.matthiaspaulscholz.eu/tools/index.html

Apart from the tools listed there, you can use the official 
programming environment that comes with the kit (NXT-G) also, of course.

Regards,
   Matthias Paul

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Lejos 3.0 RC1: Unable to load native libraries

[Matthias Paul Scholz]

Magnus and Rob,

seems you have detected a bug in the lejos script indeed - it's missing 
the export of the library path:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$LEJOS_HOME/bin

Thanks for hinting that to me.

A workaround until the next (corrected) RC version of leJOS is to set 
the variable manually as above in the shell before running lejos.

Regards,
   Matthais Paul

Magnus Korvald wrote:

 Hi Matthias,
 
 I did run ant in the lejos/build folder, and it did seem like that 
 compiled some libraries. The proses did not return any errors.
 
 Lots of thanks for helping me out!
 
 Regards,
 Magnus
 
 Matthias Paul Scholz wrote:
 
 Magnus,

 have you built the libraries on your machine (which is required for 
 the linux distribution - see readme)?

 Cheers,
   Matthias Paul

 [EMAIL PROTECTED] wrote:

 Hi,

 I have successfully uploaded the lejos firmware onto the RCX 2.0 unit.
 Now, I am having trouble uploading compiled java programs for the RCX.

 I have tried both the checkDistribution.sh script and the HelloWorld 
 with
 no luck

 It seems like lejos have some trouble loading the native library
 libjirtrcx.so, which is found in the $LEJOS_HOME/bin directory.

 I am using lejos 3.0 RC1, Linux version 2.6.9-42.EL running Java 
 1.5.0_04

 Any hints as to why I am experiencing this problem?

 Below you'll find all environment variables as well as the error message
 from lejos.

 Regards,
 Magnus


 
 
 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Lejos3 and JCreator - problems with flags

[Matthias Paul Scholz]

Roger,

As a matter of fact, it's already on my stack to look into this.
As soon as I have found some spare time and have a solution, I'm going 
to give notice.

  Matthias Paul (slightly busy presently)

Roger Glassey wrote:
 Hi Matthias,
 I see that the checkDistribution.bat  contains
  call lejos.bat -v DistributionSmokeTest
 The -v flag does not generate a  listing of classes and signatures  that 
 I can see. When delete the  -v   flag, the same output appears.
 Looks like a problem with   lejos.bat,   not with JCreator.
 I hope there is an easy fix.
 Roger
 
 

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Lejos 3.0 JCreator

[Matthias Paul Scholz]

Roger, Bob,

Roger Glassey wrote:
 Yes, I can compile and dowload Lejos 3 with JCreator.  You are right, 
 the bin files have different names.   

To my knowledge the java-based compile, link and download scripts have 
been contained in leJOS 2.1.0 already with the same names; however, the 
(even then legacy) c-based scripts have finally disappeared in leJOS 3 
indeed.

 The compiler is lejosjc.bat , not lejosc as the readMe file says.  

Ooops! Typo. Thanks for pointing that out.

 And there is another problem,  If you 
 set the -verbose flag in JCreator, then lejos.bat  fails.  Too bad, 
 because debugging is then pretty difficult.
 

Hm..sad thing. I'll have a look into this as soon as possible.

Regards,
   Matthias Paul

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Humble request for the lejos.sourceforge.net page

[Matthias Paul Scholz]

Irv,

thanks for pointing that out.

As for the leJOS 3.0 release candidate, the distributions available for 
download are linked by the operating systems they support - here theere 
should ensue no uncertainty about Mac OSX not being supported, as 
there's no link provided (we tried to produce a Mac OSX version, but 
sadly could not find developers owning a Mac who were actually 
contributing a working version).
I agree with you that once leJOS 3.0 is out and labeeled as the official 
release, a note regarding the Mac thing should be provided explicitely 
on the leJOS page.

As for leJOS 2.1.0, the actual situation is somewhat unclear to me.
The release has taken place almost four years ago and if I recall 
correctly, 2.1.0 was meant to work on Mac then.
However, obviously it does not (not completely?) work on OSX 10.4.
(I can't do any test here by myself, being not in possession of a Mac).
If this is the case, a hint on the leJos page will be helpful indeed.
Some experiences of other Mac-people with this?

Regards and thanks again,
   Matthias Paul


Irv Levy wrote:

 
 Matthias,
 
 After accidentally finding your mailing list at www.mail-archive.com, I 
 have come to learn that it is not possible to use LeJOS (as it is 
 currently available) for my Mac OS X 10.4 system.
 
 I humbly plead with you to make that information bold and obvious on the 
 main page and the download page for leJOS at sourceforge.  I spent about 
 3 days trying to make this work before I finally stumbled on the mailing 
 list which tells me that I should pretty much forget about it until 
 (unless) a Mac developer takes on the challenge.  As a professor of 
 computer science, I might be able to interest a student in that 
 challenge.  As a friend of educators, though, I would be horrified to 
 think that another colleague would spend as much time and effort as I 
 have when it could be easily stated on the sourceforge site that it's a 
 bad idea.
 
 Please?
 
 Thank you,
 
 Irv Levy
 

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] netbeans

[Matthias Paul Scholz]

William,

Presently, when you run lejosdl against an RCX without leJOS firmware, 
you will most likely get an RCX not responding error. So, in a manner 
of speaking, lejosdl notices that the firmware has not been downloaded 
to the RCX.
But there's no error recovering in the sense of automatic fixing (e.g. 
by lejosdl starting firmdl).
In a nutshell: the presence of a leJOS firmware on the RCX is a (not 
completely unreasonable) prelimitation for lejosdl working with that RCX.

To make lejosdl aware of the firmware not available on a RCX could be 
quite costly, for one had to distingusih between different possible 
reasons for a download failure - the RCX might not be switched on, 
ambient light, RCX too far away etc. The firmware not being present 
seems to be a more exotic failure reason to me in this context.

With that in mind, one would prefer a more lightweight solution here, 
even more as firmware download to an RCX is usually required only once.
It might be easier to ensure in the process that firmdl has been called 
  at least once successfully, might it not?

Regards,
   Matthias Paul


William J. Rust wrote:

 I think I finally have got the build.xml to the point of copying it into 
 an RCX project directory and it will just work. The question now is, 
 is there a programmatic way to check if the firmware is already 
 downloaded? That is, can Lejosdl automatically detect that an RCX is 
 present but without its firmware and, if so, download firmware before it 
 downloads the program? It would be helpful to be able to do that since 
 that would not require a separate step in the build process.
 
 Thanks,
 
 wjr
 


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Success -- lejos 2.1.0 running on OS X 10.4

[Matthias Paul Scholz]

Irv Levy wrote:

 Matthias,
 
 This weekend, with the help of several others, I've actually managed to 
 use lejos 2.1.0 on Mac OS X 10.4.7 with Intel Core Duo.  

Great!

 I'll put together a set of explicit instructions that might be of use to 
 others who are in the same situation. 

Magnificent. How about placing them somewhere on www.lejos.org then?

By the way, did you try it with leJOS 3 also?

Matthias


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] All's well that ends well: leJOS 3 for the RCX release candidate

[Matthias Paul Scholz]

Scott

Scott Spencer wrote:
 Well, I guess I've missed those calls, or maybe the LeJOS Mac Community 
 lies somewhere else, 

There has been a rather elaborate discussion conecerning this in 
February (if I recall correctly) on this list.

  but I think having LeJOS for Mac OS X is pretty
 important.

Yes, that was a common feeling then. But I presume nobody of the Mac 
community has found time since then for actually taking up the task.

 What kind of contributions/support was requested.  

Quite easy:
1. Enhance the ant task (and maybe dependent artifacts) contained in 
CVSHEAD/lejos/release running and doing its job in creating and packing 
a Mac LeJOS distribution
2. Test the distribution on Mac and make sure it works there

There has been some works on this over the last years, but presently 
it's not functional (according to the info I got from some Mac guys).

A very important point to take care of is not to make changes to the 
leJOS cvs content that breaks the build, release and test process on 
other platforms.

On the other hand it's not the task to just assemble a distribution 
somehow locally in a process not reproducible in the future for other 
Mac leJOS developers (well, that should be self-evident, I guess).

Thanks for your interest in this,
Matthias Paul

ps. I'd like to separate the existing leJOS 3 release (candidate) for 
Linux and Windows from a potential Mac release to-be, for there's a 
strong desire by me to bring this to an end finally.

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

[Lejos-discussion] All's well that ends well: leJOS 3 for the RCX release candidate

[Matthias Paul Scholz]

All,

Three and a half years after the last official release of leJOS and with 
Java support for the RCX's successor, the NXT, around the corner, time 
was due to incorporate the enhancements made to leJOS since December 
2006 in a final and clean leJOS for RCX release, named lejos 3.0.
Late, but better now than never, an according release candidate is now 
available in the links section of lejos.org 
(http://lejos.sourceforge.net/links.html).
In it, all the issues that have popped up in the four precedent 
milestones should have been fixed (thanks to all who have been engaged 
themself in testing these ones).

Major topics are (as a matter of fact, I had to find them out by myself, 
for a broadcast for input concerning the changes to 2.1.0 amongst those 
who may have contributed something faded away without any response - 
hence the list is most likely incomplete):

- support for Linux kernel 2.6 now
- major restructuring and refactoring of leJOS' classes
- the single lejos command for linking and downloading programs in one 
step is available again
- the tutorial is part of the leJOS release now (see doc/tutorial)
- the third party libraries have been factored out to a 3rdparty folder
- there is a folder check now that contains a script for checking the 
distribution after having installed it

As Roger hinted to me, there are some compatibility to 2.1.0 issues, as 
the Tower methods have been switched from error result code to exception 
handling.
Furthermore, there have been some complaints on problems with M4 when 
using a serial tower - that I could not re-enact, fix or test by myself.

Unfortunately, again there is no release for the Mac; I do not possess 
one by my own, and despite multiple calls for contributions to the leJOS 
Mac community in the end I could find no one who were actually 
contributing to the release.

Feel free to give the release candidate a try and provide feedback (in 
particular if you find any errors still - I tried to test the whole 
thing as completely as it was possible to me); response on successful 
usage is welcome also :-)

Regards,
   Matthias Paul



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] trouble getting newer versions

[Matthias Paul Scholz]

Christine,

 The build (required for Linux only) is done using ANT
 (http://ant.apache.org/): the build.xml actually is an ANT build file.
Changing into the build folder and running

ant

should do (well, I know, I've forgotten to add the Read.me file - am about 
to fix this presently).
Do not hesitate to report any problems with this.

Cheers,
  Matthias Paul

 - Original Message - 
 From: Christine A. Shannon
 Subject: [Lejos-discussion] trouble getting newer versions


 I used lejos 2.1 when I taught my AI course two years ago.  In getting 
 ready for Fall classes I tried to download the CVS version but even though 
 I tried to type enter as indicated when prompted for a password, it did 
 not respond.

 I then downloaded the lejos 3 preview and followed all the install 
 instructions but then I discovered there was no Makefile.  I take it there 
 is another step to create one from the build.xml ??

 Thanks for your help

 Christine Shannon 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Installing Lejos on Windows XP - bugs in lejos.exe and lejosc.exe ?

[Matthias Paul Scholz]

Morten,

Morten H Pedersen wrote:

 So the problem might be a part of the C-based tools? 
 
 Where can I find them in the CVS to try to find the problem? 
 

For 2.1.0, these files had been located in the tools folder. Yet, 
after the 2.1.0 release, the lejos file structure has been refactored 
completely and it looks like as if the sources for the C-based link and 
download tools are gone (am I right here?).

 Do any of you developers still use the C-based versions on a MS XP platform
 - I mean - do they actually work?

No, they are deprecated now.

 
 Since I had to this:
 6) lejosc view  - does not work if I do not define javac =
 C:\j2sdk1.4.2_12\bin\javac.exe  even though the path variable is OK.
 ??? 
 8) lejos does only run if I define: java = C:\j2sdk1.4.2_12\bin\java.exe
 
 
 to even make them run, this indicates there might be some bugs in lejos.exe
 and lejosc.exe, which is a shame since all older books - such as Brian
 Bagnall's refer to the C-based tools - which means people can not make lejos
 work.

Well .. the books mentioned have been written for leJOS 2.1.0, and the 
C-based tools contained in 2.1.0 should work.
Which version of leJOS are you using?

Regards,
Matthias

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Installing Lejos on Windows XP - bugs inlejos.exe and lejosc.exe ? Lejos 3.0?

[Matthias Paul Scholz]

Morten,

- Original Message - 
From: Morten H Pedersen [EMAIL PROTECTED]
To: lejos-discussion@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Sent: Monday, July 31, 2006 5:53 PM
Subject: [Lejos-discussion] Installing Lejos on Windows XP - bugs 
inlejos.exe and lejosc.exe ? Lejos 3.0?



 Maybe you (developers) could fully remove the lejos and lejosc exe-files
 from the windows distrib. if they do not work, and make .bat files with 
 the
 same names and parameters to replace them?

That would require an update release of 2.1.0 parallel to the upcoming leJOS 
3.0 one; I'm not sure if that's really worth the effort.
Any volunteers?

 Some places lejos 3.0 is mentioned - but I cannot find anything about 
 lejos
 3.0 on the web page. Is there any information anywhere and / or 
 instructions
 on how to get / use that?

See http://lejos.sourceforge.net/links.html

Regards,
  Matthias Paul 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Controlling NXT Through Java/Bluetooth

[Matthias Paul Scholz]

Brian,

this sounds promising indeed.

One question, yet: do you intend to make any changes to the codebase in 
leJOS' cvs already that refer to the NXT?

Just asking, for I'd considered it useful if there were some discussions 
amongst the project's developers on the future on leJOS in respect to 
strategies of NXT support before actually changing the present state - 
at least some first talks revealed different attitudes towards this.

Cheers,
Matthias Paul

Brian Bagnall wrote:
 I finally had a chance to get down to hacking around with the NXT 
 and Java on Thursday and so far the code can send commands to the NXT 
 via Bluetooth for motor control and speakers. It's really early now and 
 it does some funny things that I need to figure out, but there's nothing 
 stopping full control of the NXT via a PC and Bluetooth. The code uses 
 the Java Communications API, which is poorly supported for WIndows and 
 apparently quite buggy, so I'm considering moving to RXTX. (can anyone 
 attest that RXTX is a good package?)
  
 Once the basic classes are ready for accessing all aspects of the NXT 
 brick I'll try to make some sort of release. I'm trying to decide the 
 best way to do this right now. Either copy the josx.platform.rcx classes 
 so there is a familiar way to control robotics or integrate this into 
 josx.rcxcomm. Any input would be appreciated.
  
 - Brian

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] NXT info

[Matthias Paul Scholz]

Will,

I take it that you are referring to the low-level driver layer info.
For aught I know, this is expected to be provided by LEGO at best in August.

Matthias

- Original Message - 
From: William J. Rust [EMAIL PROTECTED]
To: lejos-discussion@lists.sourceforge.net
Sent: Tuesday, June 27, 2006 5:12 PM
Subject: [Lejos-discussion] NXT info


I got an email yesterday that my NXT kits had been shipped. UPS has them
 scheduled to arrive on Friday. So, when does the secret info,
 especially related to LeJOS, become available?

 wjr



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Lejos for NXT

[Matthias Paul Scholz]

Roger,

As Jürgen has pointed out already, LEGO is supposed to publish hardware
descriptions and firmware just in August, and at a first glance it seems
to be the most reasonable thing to wait until then.

I'm not aware of the legal consequences of using pre-information outside
of the MDP. Would it be allowed by the NDA to provide something binary
leJOSish only (under some different license, obviously)?

On THE NXT STEP (http://thenxtstep.blogspot.com/) I detected the
announcement of a book by Brian (Bagnall) called Maximum Lego NXT :
Building Robots with Java Brains
(http://www.amazon.com/gp/product/0973864915/qid=1150320252/sr=1-1/ref=sr_1_1/103-2540729-7108649?s=booksv=glancen=283155),
 

intended to be available at 1st of January 2007; as I'm tremendeously
looking forward to this one, I'm curious on what NXT Java environment it
will be based (well, I'm as much a layman when it comes to lead time for
a book as I am for legal aspects, but I'd presume that such a nplatform
would have to come into being in, say, the next three months for the
book to be publishable in January, hasn't it?).
Maybe Brian sees himself in the position to drop one or two words here?

Regards,
   Matthias

Roger Glassey wrote:
 I realize that Lego has not yet made public device drivers for NXT. But 
 some information is available to the MDP.  So my question is: what  
 more  is needed to port a baby version of the Lejos VM to the NXT?  
 Something that can be downloaded and runs a simple  object, for example 
 makes a sound?  I ask because I am a bit worried about some version of 
 NXT Java available for my class in September.
 
 
 
 Roger
 



___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Navigation API

[Matthias Paul Scholz]

Tom,

sounds great!
I should be decidedly interested in this for integration into leJOS 3.
Do you have some examples how to use it and maybe even some unit tests?
Thanks for your efforts.

Regards,
  Matthias Paul

Tom Denham wrote:

I have been working on improvements to the RotationalNavigator class for
leJOS, which greatly improves its accuracy especially when used for
repeatedly rotating through small distances. I also have some documentation
for this, describing all the problems that I found, and how they were fixed.

Are any of the developers interested in receiving a copy of this code for
possible integration with the main leJOS code? If not, would anyone else be
interested in receiving the code?

Regards
Tom Denham




---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion

Re: [Lejos-discussion] Out with the old problems, in with the new! :-) (Tower error: write failure)

[Matthias Paul Scholz]

Tripurari,

I've tried running the outstream example with leJOS 3.0 on Linux, and it 
worked for me.


These were the steps I performed:

1. switch to examples/comms/outstream
2. lejosjc Write.java
3. lejoslink -o Write.bin Write
4. lejosdl Write.bin
5. export CLASSPATH=.:$CLASSPATH:$LEJOS_HOME/lib/pcrcxcomm.jar
6. javac Read.java
7. export THIRDPARTY_LIBS=$LEJOS_HOME/3rdparty/lib
8. java -Djava.library.path=$LEJOS_HOME/bin -classpath 
.:$THIRDPARTY_LIBS/commons-cli-1.0.jar:$LEJOS_HOME/lib/jtools.jar:$LEJOS_HOME/lib/pcrcxcomm.jar 



Will try it Windows XP also.

Cheers,
  Matthias

Matthias Paul Scholz wrote:



Tripurari Volpe wrote:

Well, I finally got the sample outstream stuff to compile and run 
(sorta)... but now I have a new problem.


I compile and run the sample program 
samples/comms/outstream/Read.java, and run it on my PC.  It works, up 
to a point. Specifically, when it tries to create a new RCXPort, it 
runs into a TowerException informing me of a write failure...



[...]



I apologize for bothering this list so much, but I have a project that 
I need to finish very soon, and this link between the PC and the RCX 
is the last hurdle, that has proven to be an incredibly frustrating 
difficulty... All I want to do is pass some data from the RCX to the 
PC, for gosh sakes! :-)  



Well, this is most decidedly a justified request.
I'll have a look into that matter (squares with my efforts in getting a 
release candidate out for leJOS 3.0 in the next couple of weeks).





P.S: Incidentally, I notice that there's a second constructor for 
RCXPort, taking a string argument port... The API documentation says 
nothing - what exactly does this constructor do? Might it be helpful 
to me right now?



Wasn't the author of the comm layer, but as far as I can see from the 
RCX(Abstract)Port's class source code, the port argument is simply .. 
ignored.
Hence I don't know what's the use of this constructor at all (was maybe 
some compatibility issue).




P.P.S:  I gave the lower-level Tower class a try, and that actually 
worked, though a bit awkardly. I think I could manage to put together 
what I need with just this, but if Tower works, why doesn't RCXPort...?



As a matter of fact, I'd like to know also. Let's see.

Cheers,
/M







---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Lejos-discussion mailing list
Lejos-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lejos-discussion