Hello, lighting dealers:
we produce high quality par lighting
we give bottom price for these par lighting
par 54x3w rgb waterproof ip67 only sell: 120usd /pc
ind0or par 54x3w only sell: 70usd/pc
can you check our attached picture !!
let us know if you are interest?
Guangzhou City 6star Stage Lighting Factory
Company address :
Address: NO.2 BLOCK, HONGXIN INDUSTRIAL AREAR, SHIJIN TOWN, GUANGZHOU
as you may remember, we spoke about this on F2F in Brno. Our team would
prefer showing no URL for portlet projects. Clearly, one needs to define
what is a portlet project, but I am not sure what criteria come in
It would be enough if it worked for projects based on our newest
quickstarts - those ones under experimental "GateIn Portal Quickstarts"
category. They all import gatein-3.5-bom in their POMs. Is that a
criterion you can work with?
Hello and Happy New Year to everyone!
Between F2F meeting and Christmas vacations, I spend some time working on a PoC of LiveReload from Eclipse.
[My first iteration was using the Chrome Remote Debugging Protocol, but since it required starting Chrome with an extra "--remote-debugging-protocol" arg and it was specific to Chrome, I reworked on it to turn what's described below]
The PoC implements the server-side of the LiveReload protocol (based on websockets).
2 things to get it working (once you've checkout the plugin repo on github and started an Eclipse Runtime):
* on the Browser side, the user needs to install the LiveReload extension
* on the Eclipse side, the user starts his AS server and then clicks on "Enable LiveReload" on the server menu.
Then, when the use edits html/js/css content, the files are published by the server adapter on the AS server and then, the browser is notified of the (web) resource changes (with URL and not file location). Then, the extension decides which part of the page needs to be refreshed.
Of course, the notification occurs *after* the html/js/css files have been published on the server ;-)
# A few notes: #
* this PoC only works from Server Adapter level, as it made more sense and helped me resolve the file URL from the server host/port and the application deployment context.
See the "refresh" command description (https://github.com/mockko/livereload/blob/master/docs/WebSocketProtocol.m...): the command must include the URL of the changed file.
To get notified that the server deployed the resource, I use a PublishAdapter, so this is pure generic WTP API.
The only JBossAS-specific thing I use here is when I need to retrieve the server port:
but there may be a more portable manner to do it.
- one thing I did not get to work (yet) was the Firefox "LiveReload" extension. It looked as if the browser extension was disconnecting immediately after connexion, so there was no channel I could use to send the "refresh" command. That should be solved, though.
* the http://livereload.com/ doc mentions this hack:
"How do you stop that snippet from making it into production, then? Well, simple: add an IF and check location.host, and then feel free to commit and deploy."
which means that it should be possible to also support Mobile devices and BrowserSim if no extension can be installed on them.
The code is at the same location as before: https://github.com/xcoulon/jbosstools-pagereload (the old plugin has been moved to another branch)
There's another screencast for that: https://www.youtube.com/watch?v=MWoZIQwitSs
As usual, sound is low and accent is strong, but I'll try to fix that in the future ;-)
# Further developments #
Now, this also opens question of support to even wider file types, such as SASS/LESS instead of plain CSS:
* should we provide editors for those types (usual stuff: syntax coloring, validation, content assist, navigation) ?
* as far as SASS is concerned, there's no Java implementation of the processor. Would writing one in Java help us when it comes to processing SASS files to convert them into CSS and publish them ? The only way to do it is to invoke the ruby gem with JRuby - I haven't tried it yet, though.
All feedback is welcome.
I've created https://issues.jboss.org/browse/JBIDE-13383 for the issues related to fixes that actually needs to be done to make use of the new kepler target platform.
This is the issue that needs to be fixed before we can talk about releasing any 4.1.0.Alpha1.
I'm trying to clean up jira so 4.1.0.Alpha1 actually don't have anything but this issue but we currently got 80 issues open for alpha1 that needs checking ;(
As tracked by JBIDE-13336, we are creating a Target-Platform based on
This target platform will be the maximal/recommanded one. The minimal
one will remain the one called 4.2.0.c, which relies on Eclipse 4.2.0.
For the moment this choice implies that we want next version of JBT and
JBDS to work on both Juno and Kepler. If we decide something else later,
then we'll make mininal become 4.3.0.M4 too (so it will imply we'll only
Next steps are:
* Now: update jbosstools-build/target-platforms and related CI jobs to
add build and publishing of 4.3.0.M4
* When it's done: Update of parent pom to use 4.3.0.M4 as maximal.
I'll send a mail as an answer of this one when we move the parent pom.
Some jobs will fail, that will show that your component is not
Kepler-ready. You'll have to react accordingly. Any component that can't
support both Kepler and Juno at the same time will have to discuss with
the team of whether we should invest in refactoring it to support both,
or whether the component will make us drop support for Juno in next
Cheers, and I'll ping you back soon ;)
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
Do you want to sell your telescope better? So, a very nice box it can help
Now, here comes our new telescope boxes.
1. Nice design: fashion and convenient
2. Variety shape: nice, suitable for your telescope
3. Convenient: with handle, shoulder belt, easy to carry
4. Stability: with EVA insert, good balance.
5. Material: leather and wood are OK.
We are Focus Innovation Gifts Company, like it, pls e-mail or call us!
We promise to provide good quality with good service to you!
Warmly Tips： Our MOQ is 500pcs/ item, if you are looking for a
manufacturer to provide photo album box or frame, whether you are a
wholesaler or retailer , if the quantity can reach our MOQ, why not contact
Thanks and best regards.