Does GWTP (or GWTP-like functionality) ever make it to the SDK?

[dagerber]

I'm in the process of defining the internal client architecture of a larger application.
Our application should have a lifetime of 10 years. I therefore try to avoid 3rd party libraries where ever possible to minimze the risk, that those libraries get abandoned.
I will use gin and I really would like to use gwtp as well.

Now that Philippe Beaudoin works for Google, I would like to know, what the strategy of the Google Dev Team and Philippe is:
- will gwtp continue to exist?
- will gwtp be integrated into the SDK?
- will there be a new, higher layer in the SDK, that abstracts Activites/Places/Codesplitting/EventBus ?

I would appreciate a statement from the google dev team.

[Christian Goudreau]

• will gwtp continue to exist? Yes
• will gwtp be integrated into the SDK? I don't think so, there's a lot of tools out there made by Googler that aren't included in any Google products.
• will there be a new, higher layer in the SDK, that abstracts Activites/Places/Codesplitting/EventBus ? Gwtp, eventually :D

I'm not from google dev team, but one of the owners of GWTP.

Cheers,

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Ulk7IGpIj4YJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

--
Christian Goudreau

www.arcbees.com

[Jeffrey Chimene]

One of the advantages of working in the OSS ecosystem is that you have
access to source code, and the tools to build that source.

For that reason, I would not be so quick to dismiss 3rd party libraries.
To speak plainly, your task is to design an application that can be
built on time, under budget and meets design specifications. If you have
access to one or more 3rd party libraries, and they meet your
requirements, use them.

I find that the common trait of applications that have lasted more than
a decade, across different domains, is that they undergo continual
maintenance. Hardware platforms change, requirements change, yet these
applications remain part of the business' software portfolio. That such
code can be ported to other operating environments is a crucial design
trait.

What gwt/gwtp will look like 10 years hence, no one can know.
Nevertheless, you can specify them in your current design knowing that,
over the lifetime of your application, they wll serve the purpose for
which they're intended. Additionally, they will continue to function as
designed when ported to other operating environments.