brian m 15 Anos atrás Hi Bryan,is the developer network code available in the latest release?cheers,Brian Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Hi Brian,Sure, take a look at http://lportal.svn.sourceforge.net/svnroot/lportal/plugins/trunk under the package wol-portlet. Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Thanks Bryan,Brilliant stuff...so the profile page and the friends page are all in the same portlet...but it seems like the blogs are still separate. The menu bar at the top I presume just has some friendly urls configured in the main web.xml file of the site.Is there any proposed release date for all this cool new stuff?cheers,Brian Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Hi Brian, Right now everything is obviously geared toward the Liferay project, but the services and back end will be usable in other scenarios. I don't have a release date yet. How are you using Liferay, by the way? And have you created your profile yet on Liferay.com? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Bryan,Interesting stuff. I've been using liferay for a good few years now in two companies and it's really great the direction it seems to be going in at this stage. I've been the main technical lead on using liferay in a revenue assurance product in the telecoms area. Very successful product sold into all the major telecoms companies worldwide. Liferay was used as the display tier to aggregate data, charts, alarms etc.I'm also building a business focused site where i want to use some of the new social network capabilities.I love the direction you guys are going in...I've used jquery before and love it so it should make the frontend slicker and slicker.My biggest single frustration has always been the tight coupling of the portlets with the portal however. It's come up on the forums before I know and is on the longer term list of things to do I think, but it would be great to actually be able to have a liferay bundle that is totally minimal with very few (if any!) portlets.But broadly speaking...congratulations and as a long term user I think you guys are really going in the right direction. Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Hi Brian, In fact the discussion on loose coupling came up again this weekend (a few of us were in Vancouver to celebrate Alex Chow's wedding, and of course Liferay was one of the main topics of conversation). The pro side is that a modular architecture is more maintainable in the long run and you can strip the portal down to its bare essentials. The con is that there is slight overhead in putting everything through a common messaging system or what other solution you make to loosely couple things. We didn't come to a conclusion but we were thinking that there are core services (including the CMS, collaboration, and social stuff) that should stay in the kernel and other portlets stripped out. What are your thoughts? And do you happen to work at the company that built the sites for the owner of the former "pimple of London"? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Brian,IMHO the pros outweigh the cons for the modular approach. I think one of the biggest difficulties for new users of liferay is if you have to dig into the code, it's a pretty huge codebase. Having a core kernel that's small and fast I think is the way to go...but absolutely, I see your problem about wanting to keep some services. CMS, Login and basic user stuff is probably a good idea to keep...but even still i'm not sure. What I'm sure of is that there are people out there who customize pretty much every aspect of the portal...I know we did...and making that as easy as possible is just going to keep the community growing. Definitely the ability to customize the user account is going to come up again and again. I love the idea of the social side of the account...but i don't know if all projects would need it, so is it a kernel feature.It's a difficult problem i suppose, but long term, a simple clean kernel would be beneficial in loads of ways i think. I'd love to see a liferay deployment where I could even start it up with zero portlets in no time and then just drop each portlet I needed in. The database scripts, the whole lot could be modularized per portlet.The sites we built are used internally within the telecoms operators to check how much revenue they are loosing due to systems going down and not customers not being billed properly, so I don't think the public ever sees them. O2 are a customer, but i reckon you're thinking of their public sites probably, which we had nothing to do with :-) Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Brian, Thanks for sharing your thoughts. The best I can do right now is encourage you to participate in the community. Questions like these come up frequently and it'd be great to have your voice be part of the conversation. Also, if your company is interested in becoming a Liferay partner, we're going to use the Developer Network to feature key partners that have demonstrated expertise in Liferay through participation and projects. Let me know if you need more information about that. By the way that presentation is available now at the JavaOne landing page. Por favor, autentique-se para votar. Responda como... Cancelar
Bryan Cheung brian m 15 Anos atrás Hi Brian,Sure, take a look at http://lportal.svn.sourceforge.net/svnroot/lportal/plugins/trunk under the package wol-portlet. Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Thanks Bryan,Brilliant stuff...so the profile page and the friends page are all in the same portlet...but it seems like the blogs are still separate. The menu bar at the top I presume just has some friendly urls configured in the main web.xml file of the site.Is there any proposed release date for all this cool new stuff?cheers,Brian Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Hi Brian, Right now everything is obviously geared toward the Liferay project, but the services and back end will be usable in other scenarios. I don't have a release date yet. How are you using Liferay, by the way? And have you created your profile yet on Liferay.com? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Bryan,Interesting stuff. I've been using liferay for a good few years now in two companies and it's really great the direction it seems to be going in at this stage. I've been the main technical lead on using liferay in a revenue assurance product in the telecoms area. Very successful product sold into all the major telecoms companies worldwide. Liferay was used as the display tier to aggregate data, charts, alarms etc.I'm also building a business focused site where i want to use some of the new social network capabilities.I love the direction you guys are going in...I've used jquery before and love it so it should make the frontend slicker and slicker.My biggest single frustration has always been the tight coupling of the portlets with the portal however. It's come up on the forums before I know and is on the longer term list of things to do I think, but it would be great to actually be able to have a liferay bundle that is totally minimal with very few (if any!) portlets.But broadly speaking...congratulations and as a long term user I think you guys are really going in the right direction. Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Hi Brian, In fact the discussion on loose coupling came up again this weekend (a few of us were in Vancouver to celebrate Alex Chow's wedding, and of course Liferay was one of the main topics of conversation). The pro side is that a modular architecture is more maintainable in the long run and you can strip the portal down to its bare essentials. The con is that there is slight overhead in putting everything through a common messaging system or what other solution you make to loosely couple things. We didn't come to a conclusion but we were thinking that there are core services (including the CMS, collaboration, and social stuff) that should stay in the kernel and other portlets stripped out. What are your thoughts? And do you happen to work at the company that built the sites for the owner of the former "pimple of London"? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Brian,IMHO the pros outweigh the cons for the modular approach. I think one of the biggest difficulties for new users of liferay is if you have to dig into the code, it's a pretty huge codebase. Having a core kernel that's small and fast I think is the way to go...but absolutely, I see your problem about wanting to keep some services. CMS, Login and basic user stuff is probably a good idea to keep...but even still i'm not sure. What I'm sure of is that there are people out there who customize pretty much every aspect of the portal...I know we did...and making that as easy as possible is just going to keep the community growing. Definitely the ability to customize the user account is going to come up again and again. I love the idea of the social side of the account...but i don't know if all projects would need it, so is it a kernel feature.It's a difficult problem i suppose, but long term, a simple clean kernel would be beneficial in loads of ways i think. I'd love to see a liferay deployment where I could even start it up with zero portlets in no time and then just drop each portlet I needed in. The database scripts, the whole lot could be modularized per portlet.The sites we built are used internally within the telecoms operators to check how much revenue they are loosing due to systems going down and not customers not being billed properly, so I don't think the public ever sees them. O2 are a customer, but i reckon you're thinking of their public sites probably, which we had nothing to do with :-) Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Brian, Thanks for sharing your thoughts. The best I can do right now is encourage you to participate in the community. Questions like these come up frequently and it'd be great to have your voice be part of the conversation. Also, if your company is interested in becoming a Liferay partner, we're going to use the Developer Network to feature key partners that have demonstrated expertise in Liferay through participation and projects. Let me know if you need more information about that. By the way that presentation is available now at the JavaOne landing page. Por favor, autentique-se para votar. Responda como... Cancelar
brian m Bryan Cheung 15 Anos atrás Thanks Bryan,Brilliant stuff...so the profile page and the friends page are all in the same portlet...but it seems like the blogs are still separate. The menu bar at the top I presume just has some friendly urls configured in the main web.xml file of the site.Is there any proposed release date for all this cool new stuff?cheers,Brian Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Hi Brian, Right now everything is obviously geared toward the Liferay project, but the services and back end will be usable in other scenarios. I don't have a release date yet. How are you using Liferay, by the way? And have you created your profile yet on Liferay.com? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Bryan,Interesting stuff. I've been using liferay for a good few years now in two companies and it's really great the direction it seems to be going in at this stage. I've been the main technical lead on using liferay in a revenue assurance product in the telecoms area. Very successful product sold into all the major telecoms companies worldwide. Liferay was used as the display tier to aggregate data, charts, alarms etc.I'm also building a business focused site where i want to use some of the new social network capabilities.I love the direction you guys are going in...I've used jquery before and love it so it should make the frontend slicker and slicker.My biggest single frustration has always been the tight coupling of the portlets with the portal however. It's come up on the forums before I know and is on the longer term list of things to do I think, but it would be great to actually be able to have a liferay bundle that is totally minimal with very few (if any!) portlets.But broadly speaking...congratulations and as a long term user I think you guys are really going in the right direction. Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Hi Brian, In fact the discussion on loose coupling came up again this weekend (a few of us were in Vancouver to celebrate Alex Chow's wedding, and of course Liferay was one of the main topics of conversation). The pro side is that a modular architecture is more maintainable in the long run and you can strip the portal down to its bare essentials. The con is that there is slight overhead in putting everything through a common messaging system or what other solution you make to loosely couple things. We didn't come to a conclusion but we were thinking that there are core services (including the CMS, collaboration, and social stuff) that should stay in the kernel and other portlets stripped out. What are your thoughts? And do you happen to work at the company that built the sites for the owner of the former "pimple of London"? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Brian,IMHO the pros outweigh the cons for the modular approach. I think one of the biggest difficulties for new users of liferay is if you have to dig into the code, it's a pretty huge codebase. Having a core kernel that's small and fast I think is the way to go...but absolutely, I see your problem about wanting to keep some services. CMS, Login and basic user stuff is probably a good idea to keep...but even still i'm not sure. What I'm sure of is that there are people out there who customize pretty much every aspect of the portal...I know we did...and making that as easy as possible is just going to keep the community growing. Definitely the ability to customize the user account is going to come up again and again. I love the idea of the social side of the account...but i don't know if all projects would need it, so is it a kernel feature.It's a difficult problem i suppose, but long term, a simple clean kernel would be beneficial in loads of ways i think. I'd love to see a liferay deployment where I could even start it up with zero portlets in no time and then just drop each portlet I needed in. The database scripts, the whole lot could be modularized per portlet.The sites we built are used internally within the telecoms operators to check how much revenue they are loosing due to systems going down and not customers not being billed properly, so I don't think the public ever sees them. O2 are a customer, but i reckon you're thinking of their public sites probably, which we had nothing to do with :-) Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Brian, Thanks for sharing your thoughts. The best I can do right now is encourage you to participate in the community. Questions like these come up frequently and it'd be great to have your voice be part of the conversation. Also, if your company is interested in becoming a Liferay partner, we're going to use the Developer Network to feature key partners that have demonstrated expertise in Liferay through participation and projects. Let me know if you need more information about that. By the way that presentation is available now at the JavaOne landing page. Por favor, autentique-se para votar. Responda como... Cancelar
Bryan Cheung brian m 15 Anos atrás Hi Brian, Right now everything is obviously geared toward the Liferay project, but the services and back end will be usable in other scenarios. I don't have a release date yet. How are you using Liferay, by the way? And have you created your profile yet on Liferay.com? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Bryan,Interesting stuff. I've been using liferay for a good few years now in two companies and it's really great the direction it seems to be going in at this stage. I've been the main technical lead on using liferay in a revenue assurance product in the telecoms area. Very successful product sold into all the major telecoms companies worldwide. Liferay was used as the display tier to aggregate data, charts, alarms etc.I'm also building a business focused site where i want to use some of the new social network capabilities.I love the direction you guys are going in...I've used jquery before and love it so it should make the frontend slicker and slicker.My biggest single frustration has always been the tight coupling of the portlets with the portal however. It's come up on the forums before I know and is on the longer term list of things to do I think, but it would be great to actually be able to have a liferay bundle that is totally minimal with very few (if any!) portlets.But broadly speaking...congratulations and as a long term user I think you guys are really going in the right direction. Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Hi Brian, In fact the discussion on loose coupling came up again this weekend (a few of us were in Vancouver to celebrate Alex Chow's wedding, and of course Liferay was one of the main topics of conversation). The pro side is that a modular architecture is more maintainable in the long run and you can strip the portal down to its bare essentials. The con is that there is slight overhead in putting everything through a common messaging system or what other solution you make to loosely couple things. We didn't come to a conclusion but we were thinking that there are core services (including the CMS, collaboration, and social stuff) that should stay in the kernel and other portlets stripped out. What are your thoughts? And do you happen to work at the company that built the sites for the owner of the former "pimple of London"? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Brian,IMHO the pros outweigh the cons for the modular approach. I think one of the biggest difficulties for new users of liferay is if you have to dig into the code, it's a pretty huge codebase. Having a core kernel that's small and fast I think is the way to go...but absolutely, I see your problem about wanting to keep some services. CMS, Login and basic user stuff is probably a good idea to keep...but even still i'm not sure. What I'm sure of is that there are people out there who customize pretty much every aspect of the portal...I know we did...and making that as easy as possible is just going to keep the community growing. Definitely the ability to customize the user account is going to come up again and again. I love the idea of the social side of the account...but i don't know if all projects would need it, so is it a kernel feature.It's a difficult problem i suppose, but long term, a simple clean kernel would be beneficial in loads of ways i think. I'd love to see a liferay deployment where I could even start it up with zero portlets in no time and then just drop each portlet I needed in. The database scripts, the whole lot could be modularized per portlet.The sites we built are used internally within the telecoms operators to check how much revenue they are loosing due to systems going down and not customers not being billed properly, so I don't think the public ever sees them. O2 are a customer, but i reckon you're thinking of their public sites probably, which we had nothing to do with :-) Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Brian, Thanks for sharing your thoughts. The best I can do right now is encourage you to participate in the community. Questions like these come up frequently and it'd be great to have your voice be part of the conversation. Also, if your company is interested in becoming a Liferay partner, we're going to use the Developer Network to feature key partners that have demonstrated expertise in Liferay through participation and projects. Let me know if you need more information about that. By the way that presentation is available now at the JavaOne landing page. Por favor, autentique-se para votar. Responda como... Cancelar
brian m Bryan Cheung 15 Anos atrás Hi Bryan,Interesting stuff. I've been using liferay for a good few years now in two companies and it's really great the direction it seems to be going in at this stage. I've been the main technical lead on using liferay in a revenue assurance product in the telecoms area. Very successful product sold into all the major telecoms companies worldwide. Liferay was used as the display tier to aggregate data, charts, alarms etc.I'm also building a business focused site where i want to use some of the new social network capabilities.I love the direction you guys are going in...I've used jquery before and love it so it should make the frontend slicker and slicker.My biggest single frustration has always been the tight coupling of the portlets with the portal however. It's come up on the forums before I know and is on the longer term list of things to do I think, but it would be great to actually be able to have a liferay bundle that is totally minimal with very few (if any!) portlets.But broadly speaking...congratulations and as a long term user I think you guys are really going in the right direction. Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Hi Brian, In fact the discussion on loose coupling came up again this weekend (a few of us were in Vancouver to celebrate Alex Chow's wedding, and of course Liferay was one of the main topics of conversation). The pro side is that a modular architecture is more maintainable in the long run and you can strip the portal down to its bare essentials. The con is that there is slight overhead in putting everything through a common messaging system or what other solution you make to loosely couple things. We didn't come to a conclusion but we were thinking that there are core services (including the CMS, collaboration, and social stuff) that should stay in the kernel and other portlets stripped out. What are your thoughts? And do you happen to work at the company that built the sites for the owner of the former "pimple of London"? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Brian,IMHO the pros outweigh the cons for the modular approach. I think one of the biggest difficulties for new users of liferay is if you have to dig into the code, it's a pretty huge codebase. Having a core kernel that's small and fast I think is the way to go...but absolutely, I see your problem about wanting to keep some services. CMS, Login and basic user stuff is probably a good idea to keep...but even still i'm not sure. What I'm sure of is that there are people out there who customize pretty much every aspect of the portal...I know we did...and making that as easy as possible is just going to keep the community growing. Definitely the ability to customize the user account is going to come up again and again. I love the idea of the social side of the account...but i don't know if all projects would need it, so is it a kernel feature.It's a difficult problem i suppose, but long term, a simple clean kernel would be beneficial in loads of ways i think. I'd love to see a liferay deployment where I could even start it up with zero portlets in no time and then just drop each portlet I needed in. The database scripts, the whole lot could be modularized per portlet.The sites we built are used internally within the telecoms operators to check how much revenue they are loosing due to systems going down and not customers not being billed properly, so I don't think the public ever sees them. O2 are a customer, but i reckon you're thinking of their public sites probably, which we had nothing to do with :-) Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Brian, Thanks for sharing your thoughts. The best I can do right now is encourage you to participate in the community. Questions like these come up frequently and it'd be great to have your voice be part of the conversation. Also, if your company is interested in becoming a Liferay partner, we're going to use the Developer Network to feature key partners that have demonstrated expertise in Liferay through participation and projects. Let me know if you need more information about that. By the way that presentation is available now at the JavaOne landing page. Por favor, autentique-se para votar. Responda como... Cancelar
Bryan Cheung brian m 15 Anos atrás Hi Brian, In fact the discussion on loose coupling came up again this weekend (a few of us were in Vancouver to celebrate Alex Chow's wedding, and of course Liferay was one of the main topics of conversation). The pro side is that a modular architecture is more maintainable in the long run and you can strip the portal down to its bare essentials. The con is that there is slight overhead in putting everything through a common messaging system or what other solution you make to loosely couple things. We didn't come to a conclusion but we were thinking that there are core services (including the CMS, collaboration, and social stuff) that should stay in the kernel and other portlets stripped out. What are your thoughts? And do you happen to work at the company that built the sites for the owner of the former "pimple of London"? Por favor, autentique-se para votar. Responda como... Cancelar brian m Bryan Cheung 15 Anos atrás Hi Brian,IMHO the pros outweigh the cons for the modular approach. I think one of the biggest difficulties for new users of liferay is if you have to dig into the code, it's a pretty huge codebase. Having a core kernel that's small and fast I think is the way to go...but absolutely, I see your problem about wanting to keep some services. CMS, Login and basic user stuff is probably a good idea to keep...but even still i'm not sure. What I'm sure of is that there are people out there who customize pretty much every aspect of the portal...I know we did...and making that as easy as possible is just going to keep the community growing. Definitely the ability to customize the user account is going to come up again and again. I love the idea of the social side of the account...but i don't know if all projects would need it, so is it a kernel feature.It's a difficult problem i suppose, but long term, a simple clean kernel would be beneficial in loads of ways i think. I'd love to see a liferay deployment where I could even start it up with zero portlets in no time and then just drop each portlet I needed in. The database scripts, the whole lot could be modularized per portlet.The sites we built are used internally within the telecoms operators to check how much revenue they are loosing due to systems going down and not customers not being billed properly, so I don't think the public ever sees them. O2 are a customer, but i reckon you're thinking of their public sites probably, which we had nothing to do with :-) Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Brian, Thanks for sharing your thoughts. The best I can do right now is encourage you to participate in the community. Questions like these come up frequently and it'd be great to have your voice be part of the conversation. Also, if your company is interested in becoming a Liferay partner, we're going to use the Developer Network to feature key partners that have demonstrated expertise in Liferay through participation and projects. Let me know if you need more information about that. By the way that presentation is available now at the JavaOne landing page. Por favor, autentique-se para votar. Responda como... Cancelar
brian m Bryan Cheung 15 Anos atrás Hi Brian,IMHO the pros outweigh the cons for the modular approach. I think one of the biggest difficulties for new users of liferay is if you have to dig into the code, it's a pretty huge codebase. Having a core kernel that's small and fast I think is the way to go...but absolutely, I see your problem about wanting to keep some services. CMS, Login and basic user stuff is probably a good idea to keep...but even still i'm not sure. What I'm sure of is that there are people out there who customize pretty much every aspect of the portal...I know we did...and making that as easy as possible is just going to keep the community growing. Definitely the ability to customize the user account is going to come up again and again. I love the idea of the social side of the account...but i don't know if all projects would need it, so is it a kernel feature.It's a difficult problem i suppose, but long term, a simple clean kernel would be beneficial in loads of ways i think. I'd love to see a liferay deployment where I could even start it up with zero portlets in no time and then just drop each portlet I needed in. The database scripts, the whole lot could be modularized per portlet.The sites we built are used internally within the telecoms operators to check how much revenue they are loosing due to systems going down and not customers not being billed properly, so I don't think the public ever sees them. O2 are a customer, but i reckon you're thinking of their public sites probably, which we had nothing to do with :-) Por favor, autentique-se para votar. Responda como... Cancelar Bryan Cheung brian m 15 Anos atrás Brian, Thanks for sharing your thoughts. The best I can do right now is encourage you to participate in the community. Questions like these come up frequently and it'd be great to have your voice be part of the conversation. Also, if your company is interested in becoming a Liferay partner, we're going to use the Developer Network to feature key partners that have demonstrated expertise in Liferay through participation and projects. Let me know if you need more information about that. By the way that presentation is available now at the JavaOne landing page. Por favor, autentique-se para votar. Responda como... Cancelar
Bryan Cheung brian m 15 Anos atrás Brian, Thanks for sharing your thoughts. The best I can do right now is encourage you to participate in the community. Questions like these come up frequently and it'd be great to have your voice be part of the conversation. Also, if your company is interested in becoming a Liferay partner, we're going to use the Developer Network to feature key partners that have demonstrated expertise in Liferay through participation and projects. Let me know if you need more information about that. By the way that presentation is available now at the JavaOne landing page. Por favor, autentique-se para votar. Responda como... Cancelar