jMaki customizer

[Venkatesh Babu-5]

Hi ,
I am starting to work on improving the  jMaki customizer for the
netbeans plugin module. Since we are integrating the plugin code into
netbeans, i was wondering whether the way the property editor for jmaki
should work something like the way it works for the matisse/JSF/visual
web customizers. Is there a plan for moving along those lines or is it
okay for us to have the customizers work the way they presently show up
in netbeans.

-Venky

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Ludovic Champenois]

Venkatesh Babu wrote:
> Hi ,
> I am starting to work on improving the  jMaki customizer for the
> netbeans plugin module. Since we are integrating the plugin code into
> netbeans, i was wondering whether the way the property editor for
> jmaki should work something like the way it works for the
> matisse/JSF/visual web customizers.
Why not, if the content can be populated with a mix of widget.json data
and parsed data. The parsing is the really tricky part (read: hack) and
works only for jsp files currently (not php, ruby, phobos or html).
You need a strong document model, maybe the new gsf framework might help.
> Is there a plan for moving along those lines or is it okay for us to
> have the customizers work the way they presently show up in netbeans.
Improvement in this weak area is welcome. What is there is more a
'prototype' of what customizer/prop editor should be than a real clean
implementation.
Thanks for investigating and proposing new ideas there.
>
> -Venky
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Ratnadeep Bhattacharjee-2]

Ludovic Champenois wrote:

> Venkatesh Babu wrote:
>> Hi ,
>> I am starting to work on improving the  jMaki customizer for the
>> netbeans plugin module. Since we are integrating the plugin code into
>> netbeans, i was wondering whether the way the property editor for
>> jmaki should work something like the way it works for the
>> matisse/JSF/visual web customizers.
> Why not, if the content can be populated with a mix of widget.json
> data and parsed data. The parsing is the really tricky part (read:
> hack) and works only for jsp files currently (not php, ruby, phobos or
> html).
> You need a strong document model, maybe the new gsf framework might help.

What is this "gsf framework"?

>> Is there a plan for moving along those lines or is it okay for us to
>> have the customizers work the way they presently show up in netbeans.
> Improvement in this weak area is welcome. What is there is more a
> 'prototype' of what customizer/prop editor should be than a real clean
> implementation.
> Thanks for investigating and proposing new ideas there.
>>
>> -Venky
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Daoud Abdelmonem Faleh]

Hi,
Am investigating the same area. Still have no glue of what should be
done here. We could cooperate on formulating uses cases and requirements.
Am thinking of a .json lexer that would ensure respect to the json
schema of each widget.. (maybe a heavy weight solution).
Suggestions are welcome.

Regards,
Daoud AbdelMonem Faleh.

Ludovic Champenois a écrit :

> Venkatesh Babu wrote:
>> Hi ,
>> I am starting to work on improving the  jMaki customizer for the
>> netbeans plugin module. Since we are integrating the plugin code into
>> netbeans, i was wondering whether the way the property editor for
>> jmaki should work something like the way it works for the
>> matisse/JSF/visual web customizers.
> Why not, if the content can be populated with a mix of widget.json data
> and parsed data. The parsing is the really tricky part (read: hack) and
> works only for jsp files currently (not php, ruby, phobos or html).
> You need a strong document model, maybe the new gsf framework might help.
>> Is there a plan for moving along those lines or is it okay for us to
>> have the customizers work the way they presently show up in netbeans.
> Improvement in this weak area is welcome. What is there is more a
> 'prototype' of what customizer/prop editor should be than a real clean
> implementation.
> Thanks for investigating and proposing new ideas there.
>>
>> -Venky
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

--
http://kissthedots.blogspot.com/

"Le dieu n'est pas a craindre ; la mort ne donne pas de souci ; et
tandis que le bien est facile a obtenir, le mal est facile a supporter."

No virus found in this outgoing message.
Checked by AVG.
Version: 8.0.100 / Virus Database: 270.3.0/1505 - Release Date: 16/06/2008 07:20


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Ludovic Champenois]

Ratnadeep Bhattacharjee wrote:

> Ludovic Champenois wrote:
>> Venkatesh Babu wrote:
>>> Hi ,
>>> I am starting to work on improving the  jMaki customizer for the
>>> netbeans plugin module. Since we are integrating the plugin code
>>> into netbeans, i was wondering whether the way the property editor
>>> for jmaki should work something like the way it works for the
>>> matisse/JSF/visual web customizers.
>> Why not, if the content can be populated with a mix of widget.json
>> data and parsed data. The parsing is the really tricky part (read:
>> hack) and works only for jsp files currently (not php, ruby, phobos
>> or html).
>> You need a strong document model, maybe the new gsf framework might
>> help.
>
> What is this "gsf framework"?

http://wiki.netbeans.org/Gsf
Ludo

>
>>> Is there a plan for moving along those lines or is it okay for us to
>>> have the customizers work the way they presently show up in netbeans.
>> Improvement in this weak area is welcome. What is there is more a
>> 'prototype' of what customizer/prop editor should be than a real
>> clean implementation.
>> Thanks for investigating and proposing new ideas there.
>>>
>>> -Venky
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...