[Users] Is GeoExt 3 feature-complete? Looking for GeoExt form
Christian Mayer | meggsimum
chris at meggsimum.de
Wed Aug 23 10:16:43 CEST 2017
Hi Amir,
thanks for your feedback. Indeed it would be good to have more examples
showing how to implement "old" behaviour. You are warmly invited to
contribute some examples, if you want ;-)
BTW: There is a package called "BasiGX" [1], which provides a lot of
UI-components and utils for GeoExt and is built on top of GeoExt. It is
not an official GeoExt project but several GeoExt core developers are
involved in BasiGX.
Best regards
Chris
[1] https://github.com/terrestris/basiGX
Am 23.08.2017 um 06:02 schrieb Amir Alavi:
> Thanks Christian for your helpful answer
> I think it's a good idea to have those missing features, implemented
> as an example in examples section, though they are not part of GeoExt
> 3.0. This way gives users an idea of how to perform those task in
> GeoExt 3.0.
>
> Regards and hope good days for GeoExt
>
>
> ------------------------------------------------------------------------
> *From:* Christian Mayer | meggsimum <chris at meggsimum.de>
> *To:* users at geoext.org
> *Sent:* Tuesday, August 22, 2017 4:12 PM
> *Subject:* Re: [Users] Is GeoExt 3 feature-complete? Looking for
> GeoExt form
>
> Hi Amir,
> I guess by "feature-complete" you mean "feature parity to GeoExt
> v2.x". No, at the moment GeoExt v3 has no feature parity to v2 and I
> am not sure if it will have in the near future. The main reason for
> this is that the father library ExtJS is now (since v6.x) devided in 2
> toolkits. One for apps focussed on desktops ("classic toolkit") and
> one for apps focussed on touch devices ("modern toolkit"). At the
> moment the toolkit's UI components are not synchronized in their
> naming structure. So comparable components will have different names.
> Other non-UI-parts, like stores and models can be used across the 2
> toolkits. Since we (the GeoExt developers) want to support both
> toolkits we focussed on the non-UI parts (with some exceptions, e.g.
> mapcomponent). Otherwise the GeoExt code would be blown up too much
> by switching between the toolkits.
> Once ExtJS will have synchronized UI components in both tookits we
> surely can provide more GeoExt-UI-components.
> Nevertheless GeoExt is in an ongoing development process, what does
> not mean you cannot use it in production code. You can use e.g. the
> currently released version 3.0.0 [1]
> Cheers,
> Chris
> [1] https://github.com/geoext/geoext3/releases/tag/v3.0.0
> Am 21.08.2017 um 15:38 schrieb Amir Alavi:
>> Hi all.
>> Is GeoExt 3 feature-complete or it is in development process? I can't
>> find forms which were available in GeoExt 2.
>>
>> Regards
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at geoext.org <mailto:Users at geoext.org>
>> http://www.geoext.org/cgi-bin/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users at geoext.org <mailto:Users at geoext.org>
> http://www.geoext.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at geoext.org
> http://www.geoext.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.geoext.org/pipermail/users/attachments/20170823/269c99f0/attachment-0001.html>
More information about the Users
mailing list